for my internet-facing machines I black-hole everything below 1024 and move SSH to something high but easy enough to remember like 22222

My latest trick for deciding on external ports to forward is to combine the service port and the device's internal IP address. If my desktop was 10.0.1.36 and the service was SSH on port 22, the external port would be 22136. So far it's worked well, but it only really works if you force your router to only give out 10.0.1.2 through 10.0.1.99.

If I was an evil hacker I would look at that port and other variants of 22 like 2200, 2222, etc for people's ssh.

and then all you'd have to do is compromise SSH on my fully patched system

of course the point is not to be able to withstand an attack by a persistent attacker. it prevents my logs from filling up with the constant scans from scripts