With the context you've added now, I might agree. Existing projects would be a pain to rename all files compared to adding a single line to the package.json .
About new projects, I'd have to read more about this new extension, for some reason it feels like a temporary solution that'll just get merged to the normal js extension in a future release.
I’m thinking about new projects rather than converting existing projects.
One benefit I can see to .mjs is that if all extensions are .mjs it’s clear what type of project it is without the need to open up package.json.