Aggregating query during contribution search executed twice and not cacheable

There's a query that gets executed during contribution search which aggregates the contribution totals/averages/etc gets executed twice. Because of minor variations in the query, the query is not cachable, impacting performance. Perhaps the query should be run either only once, or the queries should be written to be identical so it can be cached.