Mission creep. Your init system now has a logon shell, and handles DHCPD tasks. Why is init handling logons and dhcpds?
Neither of those things are true, which is a bad place to start your argument. It shows that you don't understand systemd, at all.
systemd added a command in which to start a new shell instance, using the same shell as before, while creating a new environment for it. It did not add a new shell.
systemd is also building new network configuration client components, not server components. If they can do a better job than NetworkManager, it'll replace that project. Right now, it hasn't.
Binary log files (PUKE)
The old logs are still available. The new ones allow administrators to check the status of a process and view logs and stdout/stderr from that process. This is a significant improvement.
Extremely poor documentation
systemd has some of the best, or at least the most complete documentation among any system component I can name.
And then when you ask a fan of it why they like it, the response is "My system boots faster."
Ask an administrator rather than an end user. Or ask a developer. If you're getting "my system boots faster" as an answer, then you're clearly asking the wrong people.
Systemd has very good documentation, unit files are very clear and concise, it actually makes use of Linux features which were not widely used beforehand (cgroups). There are lots of reasons to believe that systemd is good software.