For a "service based" password manager, sure. (It can prevent the service from ever handing over your encrypted database to an attacker.)
In a local password manager, it doesn't work like that. A challenge-response mechanism can help there, but the cost/benefit analysis looks pretty different there, IMO.
If I have 15 sites in google authenticator is it such a win that 1/15th of them will allow me to reset without needing the second factor? Backing up the app or backup codes seems needed to scale to widespread 2FA use.
In webstorm/intellij say you have a react component, one export per module as you say. The import statements are a tie imo to write by hand:
import MyThing from "../../components/editors/MyThing";
import {MyThing} from "../../components/editors/MyThing";
But if it's named, you don't need to stop what you're doing, scroll to the top of the file, type out the import statement by hand, and look over at your code tree and figure out the path to the module you want.
You just type MyT Ctrl-Space and let intellij do all that for you, not even having to move out of the function you're writing.
You shouldn't code around your tools. Your tools are there to serve you, not the other way around. Also, devs on my team use vim, Sublime, Atom, VS Code, Webstorm/IntelliJ, and many more. They all work radically different for things like this.