hostnamed is responsible for your hostname. the long start time might be related to a error in the hostname setting? (dhcp issue?)
Localed is setting up locales for your system, are your locale settings correct?
Does your journal say anything about these services?
(eg: journalctl --boot --priority=err )
I wonder why systemd thinks these services are to blame for a slower boot. If I take my own system (regular desktop, stable manjao gnome) the systemd-hostnamed & systemd-lolcaled are not blocking anything in the boot proces. Es example my data and status of these services:
systemd-analyze blame ✔
3.558s NetworkManager-wait-online.service
3.536s plymouth-quit-wait.service
1.400s lvm2-monitor.service
1.295s systemd-random-seed.service
...
systemctl status systemd-hostnamed.service
apr 04 11:46:07 gid systemd[1]: Starting Hostname Service...
apr 04 11:46:07 gid systemd[1]: Started Hostname Service.
apr 04 11:46:41 gid systemd[1]: systemd-hostnamed.service: Succeeded.
systemctl status systemd-localed.service
apr 04 11:46:10 gid systemd[1]: Starting Locale Service...
apr 04 11:46:10 gid systemd[1]: Started Locale Service.
apr 04 11:46:41 gid systemd[1]: systemd-localed.service: Succeeded.