Ssh may fail when used systemd's socket activation

Clear Linux use sshd.socket to active sshd service by default .However, Using socket activation can result in denial of service, as too many connections can cause refusal to further activate the service.

#systemctl status sshd.socket
systemd[1]: sshd.socket: Trigger limit hit, refusing further activation.
systemd[1]: sshd.socket: Failed with result 'trigger-limit-hit'.

this problem is seemed the same as the #FS62248 in ArchLinux. In daemon management part of ArchLinux OpenSSH document, it’s said that

So should we use sshd.service instead of the sshd.socket too?