Too long to comment on all items, but here's a few.

- You're right. I don't know much about systemd. It's incompatible with my view of how a system should behave so I refuse to use it. In fact, I'm more likely to use Windows 10 than a Linux with systemd. I can airgap a Windows and it's still functional. I can bring in games, programs, updates with a USB stick. On Linux this is borderline impossible.

- It is very difficult to replace systemd components on system that come with it preinstalled. Too many packages are built to depend on it's ecosystem. That's why most haters describe it as a cancer. I know this because of all the shit I have to go through to avoid them being pulled in on my systems.

- I see dbus+udev+ATK as infrastructure for spyware and systemd hard-depends on it. Everything that happens in a system, including user inputs, pass through that, and the default configuration doesn't follow zero-trust / least-privilege principles. It follows "it-just-works" principles, which are the exact opposite. The way any spyware would spy on Linux system would be through these 3 components. One compromised program connects to that and everything gets leaked. Also, the default configuration is set by the package manager. Do you remember that Ubuntu had an unremovable system package called "popularity-contest"? A distro that goes enshittified may add tracking, telemetry, etc. with no user knowledge. Unfortunately, everything already wants dbus. Even Firefox wants to manage my wireless connections. Enormous breach of privileges and everybody just accepts it.

- "greater common good" - No, browsers managing wireless isn't greater common good. Auto-starting services or a network connection because some app depends on it isn't greater common good. Players that publish currently playing song on dbus isn't greater common good. It's greater Google good (replace with your workplace or your favorite trillion$ corp). There's a difference. I'm sorry you can't see it. Greater common good would be a system where the user is always root and programs are always in their own namespace/container/VM with no possibility to talk to each other unless the user manually (not automated, not by default, not even by a confirmation) sets up a communication channel. A greater common good is a system where the user can't get an "access denied" changing a system setting, not because it has permissions, but because permissions don't apply to users as they interact with system settings, admin-utils, system files. Unfortunately, Android is closer to this principle than GNU Linux.

- Can't fork systemd. 1) Because Gentoo with all their resources, paid programmers, knowledge, etc. couldn't even keep eudev alive. You expect some guy in his weekends to maintain a systemd fork?? 2) Because it's pointless. The only useful fork would be a collection of stubs that fake it's presence to allow cancer-infiltrated programs to compile, but do absolutely nothing they ask (or fake it). Firefox wants to connect to bluetooth? No bluetooth nearby. Wireless? We're on an airplane. Location? North Pole.