Although Arch uses systemd now by default, which is bad. I've replaced it with OpenRC. http://systemd-free.org has instructions if you want to do it yourself.
Last month I installed OpenBSD on my laptop, and was frustrated with its boot time.
I'm using an SSD. Debian 8 with KDE boots up in a matter of seconds. OpenBSD on the other hand needed at least 20 seconds to boot up.
I had done some research at the time, and came to the conclusion that it was systemd that allowed Linux to boot up so fast.
IIRC, OpenRC supports parallel boot. s6 and runit definitely do. And none of those are Linux specific. In fact, there have been projects to run them on BSD.
I guess you're probably right, I usually boot up just once in the morning. The truth is, being a performance freak, I expected OpenBSD to fly on my current hardware.
After much tweaking and struggle I couldn't get the DBus working, hence couldn't install GNOME.
i3wm as my window manager and manual configuration of everything especially the wireless connection were too spartan for me. So I switched back to Debian 8 + KDE.
I use i3 regularly, but I don't use wifi much. Honestly though, using netbsd with wpa or wpa2 doesn't look too hard, and you can write a script to automate the worst of it. It's by no means the horror that is iw/iwconfig and wpa_supplicant (insert ritual chants of horror and disgust).
hmm does suspend not work for you? OpenBSD is quite laptop friendly, more so than the other BSDs I'd say. If you're booting every morning then I can understand it being a bit annoying.
OpenBSD is probably the worst when it comes to overall performance of all the BSDs, and Linux.
Or rather, mimics CRUX, which imitated BSD-style init scripts.