Allow keepUnusedDataFor to be set differently based on query arguments

[LoyalPotato]

Would this be a possible option in the future?

For example if I have a search endpoint that receives the filters as arguments and I know that some are used less than others, it makes sense that I'd want to keep it cached for less time.
But the use case that interests me is in keeping just the first page of a query cached and the rest not.