Absolutely, 100% agree.
It a complete distaster and addresses a problem that wasnt even there. rc.d or init.d were universally understood and even the dummest sys admin could get something in there. On Solaris for example, nobody ever remembers how to do it or how to check when something hasnt worked so you find people shoving re-start scripts in cron instead or using some config management tool.
With a Unix system you used to be able to follow the boot process from start to login just by looking at inittab and following the trail. This was great for newbies and great for finding out why things were not happening as they should.
systemd is the one of the worst thing Ive seen on Linux (apart from recent updates to su silently breaking any script that does su - username from root and then attempts to write to /dev/stdout) but it did get me back to my old friend Slackware after many years.