Forgive me for asking but, what is systemd's main benefit? If i don't mind that my system boots up slower and in a sequential order, how does that affect the systemd's benefits for other users?
The primary benefit of systemd is that it is init done right. That means you no longer need to use executable shell scripts in order to run daemons, but can use simple text config files. SysVinit shell scripts are hard to parse for both humans and machines, while systemd .service text config files are easy to parse for both machines and people.
Integrated service management: Want to restart and important service if it crashed, but only if it crash with an abnormal exit code and hasn't been re-started the last 5 minutes. That stuff is trivial to do in systemd with only changing a simple config line in a text file. With OpenRC/SysVinite etc. , it requires endless hacking to make something similar work.
Reliable killing a process and all its sub-processes. systemd can do that because it tracks every process with cgroups, non-systemd distros can't.
Security: If SysVinit had stepped up and taken responsibility for handing out low port numbers to services so they didn't need privilege dropping code like systemd does, we could have avoided two decades of remote exploits of Linux because of wrong use of setuid in daemons. It is better to have one secure implementation of privilege dropping code made by security experts instead of letting each and every daemon try to do it.
Security: systemd can "jail"/"contain" all running services since it provides an easy to use "API" for several low level kernel security features like "Capabilities" and "Namespaces".
So the service developers, the distro-maintainers, or even the system administrator can add "NoNewPrivileges" to a service config file. That means, that even if the service is exploited, the attacker can't get escalate privileges by then exploiting another service (A typical pattern).
Extremely easy resource management like limiting a service to only X amount of memory, or CPU resources, or bandwith etc. It can do that because of cgroups integration. A single; "MemoryLimit=1G" or similar added to the service file will make things work.
There are even more good reasons. I recommend the systemd homepage, especially the "The systemd for Administrators Blog Series" for and end users perspective.
In short, for me systemd is the best thing that have happened to Linux since package management. I really like it, Good stuff that makes Linux more secure and easier to use, for both newbies and experienced admins. It also has the best man page documentation and CLI tools I have seen for many, many years. Take fx. "man systemd.index" ; that will give you an overview of each and every "man-page" related to systemd. Very nice.