Thanks, I will look at how to contribute to both.
I think that this will not be the case for every rolling release distro however. In my experience, Debian Testing (and probably Unstable as well) breaks far more often than any other RR; I partially use Void Linux as my daily driver distro and, unlike in Debian Testing, I didn’t encounter lots of bugs, let alone system breakage. Also see https://wiki.voidlinux.org/Frequently_Asked_Questions#Is_there_a_.27Stable.27_version_of_Void.3F :
There are linux distros that release to a periodic cycle, Void does not, instead provides a continual steam of updates, which makes it a rolling release. On the other hand there are bleeding edge distros, that gives the latest software as soon as possible after its release. This is not what Void does and although some software is updated frequently, it is by no means as soon as possible or come what may.
It’s all about having a good base for a security focused distribution like Whonix. Such a base doesn’t necessarily need to be security focused as well.
Are all of those 136 files specific to Whonix? I’m asking since standard services that are not specific to Whonix are mostly available for Runit as well, or maybe not even needed (for example, NM can be replaced by dhcpcd in many cases). As for dependencies, it is possible (see Runit or Void documentation, or maybe even Artix wiki for reference). However, yes, it is not as sophisticated as systemd in that regard. I mentioned sandboxing, personally, I think it’s a good thing to split up tasks between programs (UNIX philosophy), unlike systemd, which does everything itself. Thus, I recommend using an external sandbox like Bubblewrap, and yes, as I said, this would be more work.
Of course. But probably not an option for less tech-savvy users.
Xfce with Wayland would be appealing, given it will work. I just mentioned Xpra because staying on X would require that, however it’s a much worse “solution” than simply using Wayland.