Perry, thanks for chiming in. This is a typical issue that you can really comment on from a end users perspective.
I think your proposal makes it even more difficult. Things need to be simple to understand and not depend on certain other things. This is called "state" in programming and if you want to know more about why it adds so much complexity/problems/bugs please read . It's bad to have things like "it does this, but only in case you are currently doing y while setting z is a".
Hence my proposal is, having even the dev views updated automatically, because they behave like the production views. The solution to not taking to much resources is simple, just don't have many of those. I don't think on a production system, you would have your developers creating zillions of dev views. I would expect to have the development of views taking place in some dev environment, then they get migrated to the production system as a dev view, and shortly (basically immediately) afterwards, you'll deploy them as production views.
And during development you will be happy that they behave like a production view.
You just need to read the documentation once and there it will state a warning that you shouldn't have too many dev views in your production system.