The additional information can be used by changing the usual LP model to one with an additional constraint that requires the total length to be equal to the known path length (or for numerical safety, bracketed tightly from both sides but not demanding exact equality). This will still result in fractional solutions, but they can be dealt with as usual. Also the overall search is just for the first integral solution, so the tree search (if any) is small, only used as a fallback for when the cut-generation algorithms fail to find any cut while the solution is still fractional, and quickly pruned when it tries a bad guess (as this quickly results in infeasibility of the LP model).
In a quick informal test on an instance with 51 cities this helped significantly (finding the result in under 3k simplex pivots vs 13k for solving the same instance normally), but I am comparing my own bad solver against a quick modification of it, which either way does not use any fancy cuts so likely it makes the difference more pronounced than it should be.