Strange transaction input data

[papamaci90]

Hey,
I came across a token swap transaction made by a bot on BSC mainnet with a very strange input data:

0x5e2cec1e207b298f4e08facb491f13e8335969e12c912d3e0000000000000000000000000000000000001000e9e7cea3dedca5984780bafc599bd69add087d5600000000002948025f504042e364000000034a50ef0d7e8367e3976e0000000000610b0ef4fb6db57a2800000000015720d10003e3000000000000000000000000000000

If you take out the function signiture (0x5e2cec1e) and sort the inputs into 32 byte long chunks it looks like this:
207b298f4e08facb491f13e8335969e12c912d3e000000000000000000000000
0000000000001000e9e7cea3dedca5984780bafc599bd69add087d5600000000
002948025f504042e364000000034a50ef0d7e8367e3976e0000000000610b0e
f4fb6db57a2800000000015720d10003e3000000000000000000000000000000

The first parameter is clearly the pair address which was affected by the swap, in the middle of the second row there is a "1" what I don't understand but after that the address of BUSD token and so on.

My question is that what kind of solidity function takes in input data like these?
I would expect a normally padded address input in the first row like this:
000000000000000000000000207b298f4e08facb491f13e8335969e12c912d3e
The second row would look like the following without the "1" on the left side:
000000000000000000000000e9e7cea3dedca5984780bafc599bd69add087d56

Using ethers.js how can you pass an address in a contract call that looks like the input above?

Thanks a lot in advance!