There’s no need to write venomous posts. If you feel so strongly about it, you can petition the CA/Browser forum directly, since a ballot there is the only way to effect the changes you want.
Making it possible to validate the client on any non reserved port can cause no harm
The 0-1024 port reservation not universal across platforms (check Windows, you do not require any privilege to begin listening on those).
If unreserved ports are permitted as domain control validation methods, I guarantee there would be an immediate influx of mis-issued certificates.
To illustrate only one case, cPanel, by default, has a TCP range open for use by FTP connections:
ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpts:49152:65534 ctstate NEW
Unprivileged users can listen on these ports from any userland application, and instantly get authorization to issue certificates for any tenant hostname (including the primary hostname of the server/hosting company).
There are hundreds of thousands of cPanel servers on the internet today, serving tens of millions of domains (the cPanel AutoSSL CA has issued ~30M certificates in a year or two).
It is definitely not the case that this change would “cause no harm”. The issue is complex.