If I may suggest, starport auto-launch with an Imperial Cutter is exactly the same issue insofar as the reduced deceleration from Rotational Correction causes overshoot problems for the module, and it is perfectly logical that it still occurs here because the specific change was not to provide the normal deceleration while Rotational Correction is active and in effect, but to change instead the definition of when it is in effect.
The previous definition clearly was while in the vicinity of any landing pads. The stated definition now is "situations where it is actively correcting rotation", which could mean only within the volume of a starport, but may mean in the vicinity of a starport (I cannot be sure without having tried it yet). Either way, it is still in effect as before while in the volume of a starport, so auto-launch still has the same problem.
Assuming that the reduced deceleration is intended while Rotational Correction is in effect, the next ideal change would be for the auto-launch to understand that limitation and adjust its corresponding movements so that it no longer begins a lateral trajectory which it then finds itself unable to stop appropriately.