Both setups are perfectly valid:
This:
HOOKS=(base systemd autodetect microcode modconf kms keyboard sd-vconsole block sd-encrypt filesystems fsck)
uses systemd during early boot and unlocks encrypted devices using hook sd-encrypt.
While this:
HOOKS=(base udev autodetect microcode kms modconf block keyboard keymap consolefont plymouth [encrypt] resume filesystems)
uses the old-fashioned busybox + udev approach during early boot and unlocks encrypted devices using hook encrypt (the OP apparently uses this approach, but without the encrypt hook, as their encrypted home is instead unlocked by systemd during normal boot, i.e. after the initramfs has handed over control).
Regarding @Meeloo 's issue, if everything works correctly when plymouth is disabled (by removing it from HOOKS + running mkinitcpio -P), then plymouth is at fault as discussed here.