At least if it's systemd you know where to look: systemd.
And, as systemd grows ever more bloated, that becomes less and less useful. Pointing at a box and saying "the problem is somewhere in that computer" tells you nothing; only by dissecting the problem can you eliminate it. If you can't divide the monolith wherein lies the issue, there's a limit to what you can do about it.
EVERY SINGLE COMPONENT works exactly to spec, yet when you put them together, then things go wrong.
Even if that situation were to arise - and it's hypothetical, not real - systemd doesn't help you one little bit. You've still got a complex set of components, you've merely obfuscated the startup mechanism.