The "proper" place to solve this, is in the OS. Where it has been solved, including all the inevitable corner cases, already.
Why reinvent this wheel, adding complexity, bug-surface, maintenance burden and whatnot to your project? What problem dies it solve that hasn't been solved by other people?
Deployments that need to configure OSes in a particular way are difficult (the existence of docker, kubernetes, snap are symptoms of this difficulty). It requires a high level of privilege to do so. Upgrades and rollbacks are challenging, if ever done. OSes sometimes don't provide solution when we go beyond one hardware.
If "npm start" can restrain the permissions to what it should be for the given version of the code, I will use it and I'll be happy.
Getting data to literally the other side of the globe currently takes about 100 milliseconds. How many truly novel applications open up by that latency dropping to 66ms?
For short-distance stuff the latency is already low enough to be practically realtime. For long-distance stuff we're already fast enough for human-level applications (like video chat), but it's not dropping enough for computer-level applications (like synchronous database replication).
I'm sure some HFT traders are going to make an absolute fortune, but I doubt it'll have a huge impact for most other people.