

Is the rebase feature the main thing that sets atomic desktops apart?
Atomic and immutable distros essentially attempt to make each version on every computer act exactly the same to help devs with debugging. This means they shut down a lot of easy access to core system files, instead you have to use special commands to layer new changes onto your distro. These are automatically re-applied every time you upgrade, reducing the chance of breakage.
Rebasing is a fun consequence of this. Fedora Atomic images (re: things like Bazzite, Secureblue, Kinoite, etc) can be swapped out with a simple command or two. If a dev does something you don’t like, you can easily swap to a different image without having to do a full migration.
I’m not too worried about having to troubleshoot. Nobara has been appealing to me because it’s developed by the Proton guy.
Most of the kernel mods from nobara are applied on Bazzite. Bazzite and CachyOS afaik contribute to the same set of code there.
How does an atomic distro help teach containerization and data security as compared to a traditional distro?
Since you cannot easily modify system files, you need to use containers to make certain very technical (and often insecure) things work. DistroBox is the main method for this, and as a plus side, it lets you install programs with commands from any distro. I can use the AUR (an arch linux feature) on Bazzite (Fedora atomic) with DistroBox if i want, for example. There are some other things that come preinstalled on Bazzite that help with this, such as flathub and brew.sh
Steam comes preinstalled and configured on Bazzite, it isnt the flatpak version.