I do not see any evidence that there are daemons started by systemd
where systemd follows the name in /etc/alternatives on debian, or winds
up following a symlink on a multicall binary. The way I understand
/etc/alternatives I don't think you would ever want to use it for the
name of a daemon that is put in a unit file.
systemd-udevd is one example that ~everybody has installed.
(Though it doesn't use comm, it uses argv[0] to decide behaviour.)