No.
The where filter operates on the passed array based on a property of the individual items in that aray.
Not on objects, or an objects arrays
A resources tags have some convenience behaviors when working with them but they aren’t a single property which of course leads to hopeful expectations they should be useful for something like the |where: filter.
Currently this is solved with either:
A specific collection setup with conditions based on the target tag.
Or if you can do this on the client side just fetch that tag filter collection url using a special template you use specifically for ajax or the section rendering api. Keeping in mind pagination.
/collections/collectionname/tagname
What you don’t want to do is try to loop over all products in an ALL collection.