It depends on what your bottleneck is. For example on my system I get
$ systemd-analyze
Startup finished in 11.976s (firmware) + 3.879s (loader) + 2.013s (kernel) + 157ms (initrd) + 6.354s (userspace) = 24.382s
graphical.target reached after 6.316s in userspace.
The kernel boot process is only responsible for 2s of my boot time. So even if this does end up improving boot times, there's very little it can do. The real improvement for me would be to choose a faster-booting m/b. You can run systemd-analyze
on your setup to see if the kernel boot time is more significant for you.
There was a comment by one of the devs, which I've lost now, saying they misconfigured ipv6 and this caused 502 errors. It seems to be up now. We will see how things go from here.