Oh, you meant SkeletonUtility is not able to correctly position Transforms for bones on paths.
That's currently its design. Some recent changes caused some inconsistencies between the behavior of constraints in general (and where they exert their positioning), especially with the introduction of the new constraints like PathConstraint. Some Spine 3.5 changes involve making them uniform and predictable, and SkeletonUtility will be able to behave correctly in that case.
Currently, BoneFollower should work though.