No, not that I know of.

There are separate overloads of AuthenticationContext.AcquireToken that either do or do not take a userId parameter, and behave differently WRT looking up cached values. The two overloads above correspond to the scenarios where we want the caching behavior (or don't).