Today, those methods that are configured at the client-level to be non-retryable would not benefit from some ApiCallContext improvements, like supporting withRetrySettings and withRetryableCodes added in #1238, and a proposal to add a new logical timeout option. This is because the callable for such methods is not wrapped in the same context-aware machinery that retryable methods are enabling such features.

We should consider wrapping the non-retryable RPCs in the same callable machinery that would enable retries. Since the retry settings would prevent retries, there shouldn't be a behavioral issue there.