Issue or just inconvenience? `hugo new` runs long because of modules

When I run hugo new on a project with many modules (sorry, my disease is called fragmentism) it sometimes runs very long because in the background Hugo is retrieving or checking all modules for updates. I understand the necessity of this updating, but wouldn’t it be better if specifically hugo new is NOT checking for updates?

I would expect that it’s run only when I am sure my system is up to date (talking about the new here) and Hugo Modules are (currently?) not adding any functionality to either the new-process or the parsing of the archetype files. So updating the Modules at this stage would not add anything to the process of creating a new content item. Right?

Am I missing something important for the process or is this worth an issue on the GitHub repo?