You have a lot going on there James! Let me simplify my vision… This is just a quick mock up in Excel but it should give you an idea of the interface I was thinking of…
So in long form the results of that search would display only Components AND their instance name could be Door-01, Door-02 etc OR Wall-001, Wall-102 etc, AND the walls and doors all need to be tagged as being on the “First Floor” AND have a Status description contains the word “Fire” e.g. “FD60 Fire Door” or “Fire barrier”.
Having applied that search everything else that isn’t a child of the found elements in outliner is hidden when the search is run.
There are other condition options such as “Is not” or “Ends with” and case sensitive might be needing considered.
That’s it, that’s all. Any selection for editing or saving to Scenes etc then follows normal SU workflows.
Edit: While I remember this process also relies on ALL tags being ON. Otherwise they would override the visibility set in Outliner.