How do you know their code is dangerous? Have you reviewed it and published your results? Systemd is bloated? Have you even looked at the code? You do realize that systemd-init is not much bigger than sysv init was.
Furthermore, I don't think Red Hat would support systemd if their best engineers (and I know several of them; they are very smart people) doubted it. In fact if you read up on systemd you'll find that initially Red Hat was hesitant to pursue systemd. The systemd devs proved their case and won people on technical merit, especially as Linux has been moving into new areas like virtual machines and containers. And other distros are picking it up because it addresses major shortcomings that were starting to really impact Linux.
Interesting you should feel systemd is the worst of the lot when every commercial Unix out there abandoned sysv init years ago. Solaris, HPUX, Apple. You name it. They all did for the same reasons. init scripts are error-prone, clunky, hard to audit, and a maintenance nightmare. You couldn't even move an init script between systems. Have your worked with modern systems that employ containers, storage pools, logical volumes, hotplugged ethernet, storage, etc? I have, and it always was a bit kludgy before. Just consistent naming of ethernet devices is a nice benefit of systemd. Back in the dark days of Linux I would often put in ethernet cards from different manufacturers just to make sure I could map names to them in a consistent way.