ShardRemote::_scheduleCommand will update the timeout of the RemoteCommandRequest for RPCs it manages based on the remaining time left for the OperationContext the command is associated with see here

However, it doesn't update the timeout code that the RemoteCommandRequest uses by default see here to indicate timeout errors. As a result, if this timeout is hit, the networking layer will throw NetworkInterfaceExceededTimeLimit (the default RCR/networking timeout error), instead of maxTimeMSExpired, even if the timeout came from the maxTimeMS associated with the opCtx.

The function should either conditionally also update the timeoutCode for the RCR or rewrite any errors manually.