You somehow got the path's slot's bone as a child of a constrained bone? I'd be interested in how that happened. Spine should not allow that when picking the path constraint target, and if you try to rearrange the bones in such a configuration it should delete the path constraint and show a message it did so.
