The problem with the systemd environment is not amenable to patching. In
fact, the psychology of patching, more code fixes anything, is one of
the primary problems with systemd.

- From a purely mathematical perspective, aside from the ingenuous
attitude of the developers:

What is effectively a monolithic applications is undertaking too many
non orthogonal tasks. As such, it is not possible to compute a realistic
level of complexity nor fully realize completeness even in a restricted
topology. It is, in fact, a typical hacked together application without
regard to synergy, predictability, order of work, optimal algorithms and
orthogonal design.

Compatibility is not a necessity. If Linux moves in multiple directions,
so be it. Systemd, Gnome and KDE and other do everything in one fat and
potentially pathological package. Such venues are usually the product
Microsoft but it would seem that many ordinary users are now tired of
the cost and inability to move MS products to new machines and are
looking for a free or mostly free alternative. Most end users are
convinced that computers and especially software is inherently not
reliable. Software is not inherently unreliable; if it were, there would
be a lot more aircraft crashing and cars doing unusual things.

To reiterate, more code does not necessarily cure a bad application,
particularly when the design of the application is poor and/or its
working topology is ill defined.