I agree 100%
This would also be ideal if one has a "dev" or "test" version of an important bot. Those that are deeply integrated with external services (e.g. Slack, Salesforce, etc.) are difficult to test with the studio console alone.
I will probably set this up for my internal knowledge bot as we have it purely accessible from our Slack workspace. The studio emulator does help me test some changes but not fully. I can't simulate Slack DM, channels, mpim, emoji reaction, etc. I may need to test Slack API calls to get full names and more. I have to publish my changes before they're fully tested which is risky.
Additionally, once we start integrating with our Salesforce account, I'd like the dev-version of the bot to use our Salesforce Sandbox to test workflows that can write and update data in Salesforce.
To do proper testing, I therefore need to export my production bot and re-import it as a separate bot. I'd like to test changes in the dev version and then copy a full node across the two bots with just a copy and paste (I would adjust the transitions after it's pasted).
I know that I could probably export and import the dev bot to make it the production bot but that feels too risky at times.