After going through the ObiSolver code, I found the suspect, and the reason is pretty stupid, as it always turns out to be 
In the example I sent you, the solver component resides on the object that's being moved - if I move the solver to a stationary object, the glitching doesn't happen anymore. Still, it might be something you might want to look into, the problematic setup used to work correctly in older versions.
Edit: of course, unparenting the solver opened the whole other can of worms, and from what it looks like we'll have to stay on 3.2
In the example I sent you, the solver component resides on the object that's being moved - if I move the solver to a stationary object, the glitching doesn't happen anymore. Still, it might be something you might want to look into, the problematic setup used to work correctly in older versions.
Edit: of course, unparenting the solver opened the whole other can of worms, and from what it looks like we'll have to stay on 3.2