Yeah, you’re right that none of these approaches is ideal.
The reason being there’s just one continuously stored “global” speed (coming from CC) that’s redistributed to each slot as we cycle through them.
If the macro is running in a loop, it’ll adjust the speed of each looper we jump to with the global value.
We could try working around it by implementing additional change listener in macro, but that’s cumbersome and not an ideal design anyways.
I guess a more ideal approach would be to expose direct parameter in midi automations, as we have for stop/overdub etc… but I understand that takes effort on your side.