I would object that people who admin linux systems would not readily introduce cruft that makes their system more difficult to maintain.
But we are dealing with rather big companies that make bucks with supporting linux. And GNU/Linux, unfortunately for them, was getting easier to admin. When you used to compile you have packages. Even compiling modules into the kernel is automatic with dkms now.
So the linux support companies find themselves with a problem they share with the hardware companies. GNU/Linux works too well.
One solution is to bring rockstar developers to design the parallel of the windows registry. I say rockstar in an ambivalent way. One with outstanding coding skills but with a reality distortion field so bad that when his debug flag creates problems to the kernel devs he says "fix the kernel not my problem".
WHAT?
RedHat should have told him "Now you take a CS 101 course and relearn about namespaces and about not interfering with other people already established conventions, especially if it's the fucking KERNEL, you NOOB" - of course this would be the official public watered-down response.
So, everybody is happy. Hardware companies, support companies, and the horde of developers that prefer to roll out their own stuff instead to contribute to existing projects so they get fame and maybe a few bucks.
Luckily for the user, if enough clear thinking old school hackers exist, they will modularize or come up with drop in replacement for the systemd monolith. Else, better start exploring a plan b with genode, bsd, slackware, because the windowsification of linux won't stop here.