Expose per operation timeout compatible with CancellationToken

I would really like the granular control of choosing the timeout per operation. There are many Get operations that I would really like to have a very short timeout, other Gets to have a medium timeout, and Set operations to have a very long timeout. I expected this to be a very common use case.

I use the implementation wrapped from IDistributedCache in the Microsoft.Extensions.Caching.Redis library. I was deceived in thinking per operation timeout was already implemented due to the IDistributedCache implementation exposes overloads that take a CancellationToken. I've recently found out that these tokens are only used to cancel between calls to the StackExchange.Redis library and not passed to StackExchange.Redis at all.

Can we get per operation timeouts implemented? And in a way that either takes a CancellationToken directly or can be adapted from a CancellationToken?

Can this be plumbed in to be ready for Socket to support CancellationToken?

Start by tracing the IDistributedCache overloads that accept CancellationToken into the StackExchange.Redis operation path, and review how cancellation currently behaves between calls. Define the per-operation timeout and CancellationToken compatibility behavior, including the planned Socket support, then verify that Get and Set operations can use distinct timeouts without breaking existing callers.