Is there a concept of scope or nested contexts within EF Core DbContext?

Let's say my application's DbContest is scoped to the http request. The way I would do it normally is any method that needs to make changes, simply makes changes to objects loaded up via DbContext. Then at the end of the http request, I call SaveChangesAsync to ensure all changes in the change tracker are applied at once on a transaction.

However, what if in the middle of that I want to fire a separate save - maybe its an update to a cached value - I would like to fire that save without everything else in the change tracker coming along for the ride. Is there some way of creating a "sub-context" or nested context, or whatever the concept would be called that would allow me to do that?