Deno did pick a standard: the standard of the browser. Deno more directly aligns with the web browsers versus Node "standards" that were designed almost intentionally to be incompatible with web browsers. Most of those libraries you point out are all getting rewritten for ESM (a seven year old standard from 2015, mind you) and better browser compatibility anyway as Node itself finally slowly aligns with web standards. Just because they aren't all "necessary" rewrites doesn't make that all of them are "not useful".
The good news is that in this case the "competition" seems healthy: Deno's efforts have spurred Node forward to better embracing standards they've notoriously avoided before (or at least have been slow to adapt to). Deno's efforts have helped make Node more solid in its ESM support, as a big for instance. There's still an optimism that Deno and Node will again converge sometime down the future.
A thousand times this. People were so grossed out by Deno resolving imports from URLs... but browsers have allowed this forever, Deno was just aligning to how the web already works.
The good news is that in this case the "competition" seems healthy: Deno's efforts have spurred Node forward to better embracing standards they've notoriously avoided before (or at least have been slow to adapt to). Deno's efforts have helped make Node more solid in its ESM support, as a big for instance. There's still an optimism that Deno and Node will again converge sometime down the future.