Would this affect behavior at all?

One possible issue I can think of is that it won't stop sprinting in the places where it currently stops. Right now, the beginning of every movement turns sprinting off with setSprinting(false), then it's up to the movement to turn it on if it wants to sprint.

If we changed it to a keybind, then as long as W is held, it'll keep sprinting as you can just tap CTRL you don't have to hold it for the whole time you want to sprint. I could see this causing it to overshoot and miss a descend and right angle turn after a bunch of traverses.