I think part of the very reason some folks like you don't like to use some of those things is their shortcomings... which likely come about in part due to the plethora of choices leading to fragmented efforts on the development side. People shift their attention to the newer/shinier things all the time, and nothing ends up becoming rock-solid to the point where you wouldn't even think about wanting to replace it.
To put this into perspective, consider how bizarre it would be to hear end-users complain "What if I want to replace the Windows Audio/Task Scheduler/etc. service with something else?" in Windows land.
Linux has always been about software freedom and open source, it was never about choice. When people made it about choice, infinite fragmentation started and there's no end in sight.
Though with their shortcomings, thankfully somebody is fighting against that concept, and trying to build a stable base for everybody.
Of course this leaves the door open for "choice", but it's just, in my opinion, an unfortunate side effect.
That is explicitly about choice.
Pretending that freedom of choice about what people spend their free time on is "an unfortunate side effect", is what represents a "toxic" attitude in my opinion.
And people have tried a LOT to replace stuff in Windows, it is just that Microsoft doesn't make it as easy as on Linux.
In Windows Vista, Microsoft rebuilt the audio stack on top of WASAPI, making MME and DirectSound shims which feed into WASAPI. However, they didn't break compatibility, and all APIs more-or-less work nowadays. On Linux, ALSA apps sometimes have trouble picking the right device when talking to PulseAudio, and it's difficult for PulseAudio and Jack to share a single device.
And it was great when it worked, I tell you that!
So yes, they did break compatibility.
Because of the fragmentation, I don't have to use systemd, or pulseaudio, or snap, or Gnome desktop, or most other things I don't want to use for whatever reason. I can configure my box (or my container) mostly the way I see fit.
If you want ultimate unification, choose macOS. These guys are certain that they know what you need, and rid you of the need to choose. If you want a bit less strict unification but with backwards compatibility, choose Windows.
BSD sees less fragmentation mostly because it's less widely used. Though FreeBSD, OpenBSD, NetBSD, DragonflyBSD, and even Darwin exist, and differ significantly form each other. The BSD land, fortunately, also offers choice.