If I understand correctly you are proposing to introduce side effects to proxy authentication code: not only that code will perform authentication, but it will also store state of its intermediate operations. 

I don't think this is a great idea -- it introduces coupling between what now is separate bits of functionality and makes it harder to understand the code.

Instead (in case this is a problem at all) I suggest to: enable caching of sql queries and update Resolver to cache responses based on  record ttl, both of which are clean ways to resolve potential performance problems.