Feature Request: Invalid sshd port fallback

[Stop Spazzing]

I would like to suggest adding a fallback in the event that somehow the
sshd_config port number is invalid.

Example:
Port !=  (1<= or >=65535)

By default fall by to port 22, and spit out an error. Same would go for if
the new port is already in use, fall back to port 22 and spit out an error.

Why is this a good idea? Would be a good idea because people are human and
make mistakes, and you shouldn't have to wipe your server just because an
invalid port was used by accident.

Why is this a bad idea? I see no reason why this would be a bad idea that I
am aware of.