I did just read I think 90% of that, and it just seems like that person is sour about systemd in general.
I agree it's not unix/Linux philosophy but it's the best we have.
Does it do too much? Maybe. I haven't seen that exploited on a large scale in the real world, but it's definitely a golden key.
There are options. But it's just one of those things. You're pissing in the wind unless you're willing to write it yourself. You can use non systemd distros or even use bsd.
All that said, you're absolutely right to be concerned, but speaking on it like it's an active vulnerability is dangerous.
It's also evident that it's reliant on the software you run, it's not systemd that's giving you away, it's your application that you chose to install that's abusing or neglegent of systemd's access.
But that's not at all what I asked you or what you claimed. Those are technically two different things. And not technically like yes or no. Those are entirely different security fronts.
You've got to back that claim up or take it back, and I have a feeling you'll be taking it back.
It's okay to be cautious, and it's especially okay to warn others of trajectories that could lean into privacy or security issues, but it's not okay to make shit up.
Lastly it's no longer an init system. It's a system that happens to handle init.
They'll change the hats, gotta sell cheap tacky merch somehow