Specifically, under /usr/lib/systemd/system, I have the following:
lrwxrwxrwx 1 root root 55 Feb 18 06:46 dracut-cmdline.service -> ../../dracut/modules.d/98systemd/dracut-cmdline.service
lrwxrwxrwx 1 root root 57 Feb 18 06:46 dracut-initqueue.service -> ../../dracut/modules.d/98systemd/dracut-initqueue.service
lrwxrwxrwx 1 root root 53 Feb 18 06:46 dracut-mount.service -> ../../dracut/modules.d/98systemd/dracut-mount.service
lrwxrwxrwx 1 root root 57 Feb 18 06:46 dracut-pre-mount.service -> ../../dracut/modules.d/98systemd/dracut-pre-mount.service
lrwxrwxrwx 1 root root 57 Feb 18 06:46 dracut-pre-pivot.service -> ../../dracut/modules.d/98systemd/dracut-pre-pivot.service
lrwxrwxrwx 1 root root 59 Feb 18 06:46 dracut-pre-trigger.service -> ../../dracut/modules.d/98systemd/dracut-pre-trigger.service
lrwxrwxrwx 1 root root 56 Feb 18 06:46 dracut-pre-udev.service -> ../../dracut/modules.d/98systemd/dracut-pre-udev.service
lrwxrwxrwx 1 root root 56 Feb 18 06:46 dracut-shutdown.service -> ../../dracut/modules.d/98systemd/dracut-shutdown.service
drwxr-xr-x 2 root root 4096 May 25 10:05 initrd.target.wants
drwxr-xr-x 2 root root 36 May 25 10:05 sysinit.target.wants
While, admittedly, my knowledge of a working systemd install is limited (as I've managed to avoid it, and am ceratinly no systemd expert), that doesn't look quite standard (again, I could be wrong).
On the surface, it looks like some sort of workaround, or partial install, using the systemd directory as a means for fulfilling some expected dependencies for dracut.