Context: TokenTransferrer.sol#L72
The extcodesize check is only done here. In contrast, the Openzeppelin implementation would do the extcodesize check before calling the function. Heres where this function and OZs safetransfer would deviate: the token address is a precompile (so extcodesize() == 0), but it can still return data. For the same calldata abi.encodeWithSelector(ERC20.transferFrom.selector, from, to, amount):
There were some concerns of being able to spoof this function source.
Its also arguable that this is really a problem. Since 0.8.10, the high level call ERC20.transferFrom(...) would skip the extcodesize check because its always followed up by a abi.decode(...). But transferFrom is a bit of a grey area because it needs compatibility with non-compliant ERC20 tokens like USDT.
It is hard to make a proof of concept for this. In the future, a new precompile may change this. 
Consider adding an extcodesize() check before call. However, this adds an extra 100 gas and we can understand if the protocol decides to not implement this. :)
