Так и решения то стандартные. Открывая Timeouts and cancellation for humans видим Cancellation token. Только пробрасывается скрыто:

You should think of with open_cancel_scope() as creating a cancel token, but it doesn't actually expose any CancelToken object publically. Instead, the cancel token is pushed onto an invisible internal stack, and automatically applied to any blocking operations called inside the with block. So requests doesn't have to do anything to pass this through – when it eventually sends and receives data over the network, those primitive calls will automatically have the deadline applied.

Только зачем он пишет о превосходстве своего решения на Python над примитивами из C#, Go. Примитивы на то и примитивы, что на базе них можно сделать высокоуровневые абстракции.