>Paint over init and cron, pam and login. Put all of that into PID1 along with dbus
Init is in PID 1 with systemd, and it is pretty natural for an init system that can already trigger on various events to also support triggering on absolute and relative times. As for dbus, PID 1 does expose a private dbus interface, but it is NOT the system dbus daemon. Logind, journald, PAM, the dbus daemon - those are NOT in PID 1
That line just shows you are completely ignorant or a troll, or both.
It is fine to have some issues with systemd, I do myself, despite being overall in favor of it, but at least have them be real issues...