75 zones is just under 1,000 caches. To match a cache to a zone takes time depending on the complexity of the geometry of the zone. It can vary from a few seconds to a minute. 75 times that volume is not something you're going to wait for.
Then there will be the folks who don't want a state because they're near a border, so only want the closest 10 zones so we would need to be able to filter them.
Then folks will want to filter our certain cache types like mystery or trigpoints.
Then folks will want to filter out anything that's too hard like a difficulty of 4 or a terrain or 4.5 or 5.
Then folks will want to exclude micros.
So we're looking at a fully blown query engine like we have for caches, but also inclusive of zones.
The My Query generator only handle one zone at a time because anything to much larger is a huge drag on the server.
Try pasting as text instead of HTML. That might be a little better.
So while it is not immediately practical to make what you want, we could create a page like http://geocaching.com.au/dragonzone/zonecontrol/
but in state columns rather than by clan. i.e. All zones under Victoria with the counts of caches controlled. That would not let you see what caches are easy targets, but would show you what zones may be controllable. Unfortunately we don't provide data warehouse capability to extract and query what you want. In part because the cost of providing the data in CPU time and real time is outside our bounds. As you know we also suffer a hardware issue which is trying to be resolved but progress is glacial.
Maybe when we have the new hardware we can look more into a feed where you can shape and play with your own data in your own environments.