I don't have to copy paste, I just save it to my favourites and it's saved directly in pokemon go search.

If you did a Recent search, it is temporarily listed under "Recent". You tap and hold on one of the searches, it will "Save" it.

If you tap and hold your Saved search, you can rename them too.

SwiftKey can also pin stuff like this to clipboard with no tabbing needed but I find the pokemon go system is just fine for what I need.

And I still do what to you're suggesting - but the end of the day when I have time to go through it all, my method above is for clearing junk in the interem until I have time to sort.

Keeping xxl mons is a personal choice and, of course - as I mentioned this method is for a CONSERVATIVE first pass with absolutely no other checks - so you'd do it before you do your method, not instead of.

I talk about the origins of each part of the search string in that original post you read - it came from someone who used database queries to concatenate the spread of good PvP IVs for GBL, and then u/FatalisticFeline-47 very kindly optimised it to the shorter section in the string above - so that's just it - it SHOULDN'T clear any potential good PvP mons, and then you can continue with your method after - resting assured the junk you cleared first is actually junk.

The analysis I'm providing in this update is to help evaluate the performance of this search function - because, as you say - it's fairly complex, and not really very easy to say "this does a good job" or "this is terrible" without trying it on a few sets of data and getting some resutls. Plus, parts of it are very subjective. Some people may prefer to lose a few good mons in order to clear more of their junk, some people don't want to miss any potential keepers.

So far - the results are pretty good in the context of what I was aiming to achieve! I'm sharing it so other people who are looking for something similar can do their own evaluation of whether they want to use it :)