Thanks. I have a couple of thoughts to share:
Back in the day, IBM did a usability study. An application requiring the user to specify operations and fields for data input was setup two ways:
One way was manual, lots of clicks, and or input sequences. Each one did a specific thing quickly.
The other way was highly automated and the user was only required to click a few times. The tasks were the same. This way had more flow, fewer discrete commands, more functionality woven together.
To their surprise the users felt they were more productive with the software they clicked more, despite the automated version being less work and the workflow more efficient.
I bet the effective reduction in your search is minor, but the delays do accumulate and demand attention.
Given that, a small change to your flow may well change things!
What you should do is rapidly input your first queries and then as they appear, drill down on those, and when that appears, start to eliminate dead query windows, or drop fresh queries into them.
What you prefer, to use a car analogy, is one that corners like no other. Then you find yourself in one that lacks corner cases.
So you maximize your time in lane, straight road, batching the corner driving and flooring it on the straights.
I used to experience a similar thing running a browser on IRIX vd NT. The NT browser was quicker to respond where the IRIX one would delay a little and then just render it all quick
I just started working with a few windows. Changed everything. I would be typing in new queries while one I waited for was about to render.
It was a change from rapid fire to a more batch mode. Soon, I rarely had to think and my flow was fast all around.
I put this shared experience here in the hope you may be inclined to try different things.