I am under the impression that the main issue here is trying to override the velocity of the component rather than having it do what is needed. It’s somewhat similar to setting velocity of a simulation and expecting it to simulate correctly. It might, it might not.
What if you swapped it for Add Movement Input instead? Could that work? Here’s what I mean:
This would produce consistent frame independent results (thanks to the Movement Input doing its magic). Essentially, we ask the comp to move faster but it can still make its own calculations.
You can still work in the curve and the direction, but perhaps the curve should affect the Max Acceleration and / or Max Walk Speed if the TL’s track → Scale Value does not provide enough granularity and control over the movement feel - I believe this is worth experimenting with.