Hindsight.
You would know to run netstat or lsof if you have expected something like that to happen. It certainly wouldn't ever cross my mind to have sshd socket-activated and systemd actively trying to hide the fact. This change by Canonical was out of the blue, totally unexpected.
`systemctl status ssh` shows, that it is socket-activated:
[Oh, checking the entire thread for context; never mind]