I've glanced at the files of the movement range mod, and I don't see any obvious problems.
My guess is that you'll need to make a few more changes to PythonCallbackDefines.xml. In K-Mod, there are a lot of new options at the end of PythonCallbackDefines.xml, and all of them are defaulted to 'off' (ie. zero).
I'm sure that the movement mod needs one of the culture callbacks which is currently disabled, but I'm not certain if there are any others it needs. So I suggest you try setting all of the K-Mod defines to '1'. (ie. In PythonCallbackDefines.xml, below the line that says "K-Mod extras", set everything to '1'.)
The reason I've got them set to zero in K-Mod is just that it's faster for the game to not use the callbacks. So I've basically just disabled any callsbacks which aren't used for K-Mod. At the time when I added all those options I was under the impression that callbacks were one of the big speed bottlenecks in the game. But now that I know a bit more about the game I know that only some of those callbacks would make a noticeable difference, even those probably aren't a big deal most of the time. So unless you feel like carefully checking the mod's code to see exactly which ones you need, I reckon you should just enable all of the K-Mod extras.
