softdrawart
Hello, I've checked the project.
The issue that is causing this behavior is the incorrect constraint order coupled with the fact that bone22 moves in setup after the transform constraint is applied.
What happens is that constraints are calculated from top to bottom in the constraints node, and the transform constraint "bone20" is applied AFTER the path position is determined by "dzsdfs" resulting in the bones moving because they are following the constraint applied after.
To fix this:
Move the constraint "bone20" at the very top of the constraint node list, and only then attempt to reparent the bone.
More about constraint order if you're curious and would like to understand this better:
http://esotericsoftware.com/spine-constraints#Order