Oh not at all. If it does break this it's only in a relatively minor way (it's all dependent on scenario module load order and I'm not really sure how that is decided, maybe based on the order they were installed?). But old version of Tarsier break in one of the worst ways possible. It interrupts the scenario module loading process, preventing any further scenario modules from loading. Many mods are completely dependent upon that happening (SCANsat won't work at all, for instance).

This line, which shows up every time a new scene is loaded, is one of the first things I look for when I see Tarsier in the list of installed addons.

[TST]: Getting Telescope Galaxy Status
NullReferenceException: Object reference not set to an instance of an object
at TarsierSpaceTech.TSTProgressTracker.OnLoad (.ConfigNode node) [0x00000] in :0
at ScenarioModule.Load (.ConfigNode node) [0x00000] in :0
at ScenarioRunner.AddModule (.ConfigNode node) [0x00000] in :0
at ProtoScenarioModule.Load (.ScenarioRunner host) [0x00000] in :0
at ScenarioRunner+ .MoveNext () [0x00000] in :0

Although this is an old bug, and was kinda fixed. I have refactored this part of the code. Deploy in net release.