I might be completely misreading this about sustemd-homed (that is not a typo), but this is my take on it.
First, systemd refuses to let users have processes running after they leave. Apparently there's an option or configuration setting to stop this, but this is crucial to this homed stuff. Of course, all the users that like to leave screen running with a process in the background have rightfully been told by systemd that they cannot do that anymore. Bad users, thinking they can use the system how they wish. Terrible users!
Second, based on the supposition of the first point, homed now assumes everyone logs out (making the option to turn off making users log out redundant). Way to give them an option they can't use. I guess systemd truly is all about choice. LOL
Third, imagine the scenario of a user having encrypted home, not accessible by root and urgently required report sitting in there? Answer, give root access? So, what's the use? Why even bother with encryption on home? Want to encrypt something, use PGP or the likes.
So, in summary, like most of systemd (if not all), it's an answer in search of a problem. It invented problems with syslog, so it wrote journald. It invented problems with core dumps. It invented problems with DNS. It said users need a watch process to restart every daemon that fails. Don't bother fixing the daemon, just restart it until it crashes again, then restart it. It's nonsense and I am so glad BSDs stay away from it.