I tried Fedora Atomic for a while and my takeaway from image-based distro is that they would work fine for fixed workflow, but you take an hit to versatility. The biggest pain point for me was Emacs. It’s one of the major hub in my computing experience and having workflows strewn across containers doesn’t help.
I personally run Fedora Kinoite (the KDE equivalent of Fedora Silveblue) and Emacs works fine for me. I ended up installing it as a sysext[0] and it works just fine. I did also use it at one point both in a toolbox container and a flatpak, but it always felt a bit flaky there.
But honestly, since Emacs is so core to my personal workflow, I think that it's fine to use a system extension for it. Alternatively it could be layered on, which would also of course work. After that, interacting with the containers is of course just using TRAMP to "connect" to them, and that of course works just fine.
[0]: <https://github.com/fedora-sysexts/fedora> & <https://fedora-sysexts.github.io/fedora/>