corosync not being supervised by systemd

[are]

I'm looking at why corosync isn't automatically restarted on a failure (like when OOM kills corosync).

The options (Restart and RestartSec) are commented out and mention "corosync with enabled watchdog service".

Well, these options are actually unrelated to watchdog and IMO would be good if default proxmox config came with these enabled.

Any reasons against that?

Other services have that enabled:
pve-cluster.service:Restart=on-failure
pvedaemon.service:Restart=on-failure
pve-lxc-syscalld.service:Restart=on-failure
pveproxy.service:Restart=on-failure

$ systemctl cat corosync.service
[...]
# The following config is for corosync with enabled watchdog service.
#
#  When corosync watchdog service is being enabled and using with
#  pacemaker.service, and if you want to exert the watchdog when a
#  corosync process is terminated abnormally,
#  uncomment the line of the following Restart= and RestartSec=.
#Restart=on-failure
#  Specify a period longer than soft_margin as RestartSec.
#RestartSec=70
#  rewrite according to environment.
#ExecStartPre=/sbin/modprobe softdog

Edit: aded enhancement request https://bugzilla.proxmox.com/show_bug.cgi?id=3281