Depending on the purpose of your extension, configuring an activation condition could prevent it from running in your extension workspace. This setting would also benefit your target users by not unnecessarily using resources on their machines if your extension isn’t needed.
Otherwise, a feature discussed in this topic sounds like it could resolve the issue you’re experiencing. The idea is that you’d be able to toggle whether file changes cause the extension to reload. I’m a fan of this approach myself. 