Well I think part of the problem may be that in a DAW we might run far more tracks in parallel with far more effect on inserts and throughout the signal chain. In an NLE like Resolve traditionally editors have stuck to either editing with some effects or grading. In either case I actually think the burden on the computer is simply different, and that it may be easier to get away with something like this in an NLE. That’s just me guessing though.
Either way, the only alternatives I can think of here are using a) multiple projects loaded, but only activating one at a time (since that’s the maximum). This would I think get you pretty close to what you’re talking about because you can have your sfx-build project open and active and do what you need and copy finished events over to the other project’s window before it’s activated… b) work with multiple folders and deactivate the sfx-build folder/tracks when you’re not using it, or c) use playlists (forget what it’s called in Nuendo… “track versions”???). This is probably the least elegant solution.
Intuitively, to me it seems like using different projects would be the better option. For me when I do TV work I never have so much sfx work to do that I need a different “timeline”, and the few times I’ve done a lot of sfx work I’ve simply created a separate project/session for it, regardless of whether it was PT or Nuendo I was working in.
I’d love it if other people chimed in on this since workflows are always interesting to read about. Always something to learn and make work more efficient…