You can specify a different NodePort range in the apiserver
--service-node-port-range portRange Default: 30000-32767 A port range to reserve for services with NodePort visibility. Example: '30000-32767'. Inclusive at both ends of the range.
I did not try myself, but at first sight I couldn't see any place limiting the port range space, so it seems to be possible to use NodePorts on low ports
However, I do agree with Tim comments on the issue, that is opening infinite possibilities of networking going wrong, and I personally think that it should be done at the cluster admin own risk, i.e. I do not think that sig-network should triage issues related to: "I have my NodePort listening on port 443 and my cluster stopped to work", "When I configure NodePort range from 0-1024 I can not ssh into my nodes", .... ;)