If you can work out what is being sent you can recraft it and send the raw data with a normal transaction, just the steal function sig and pad your values correctly. 

Can see they have exactInputSingle(), so you can guess that and similar Uniswap functions are also in the multicalls, search signatures in the [4byte directory][1] and break the calls down:
[![searching function sig][2]][2]

Could also write your own abi for that function or take from a contract with the same function and arguments. Look up sig/arguments on 4byte directory.

Have done with an unverified farming contract that was just passing pid, amount and address to withdraw.
Something like: 

[![a minimal abi][3]][3]


  [1]: https://www.4byte.directory/signatures/?bytes4_signature=0xbc651188
  [2]: https://i.sstatic.net/9Bm0M.png
  [3]: https://i.sstatic.net/zjOH7.png