I sent a simplified attached test scene, looks like it didn't go through.
But, a bit more testing showed that if the curve is freshly re-parameterized to 0-1 then it will work. If you move any of the CVs/change the curve length, it will not.
So, seems like it's related to curve length rather than parameterization.
I guess a solution might be to write an expression to divide the curve length by the number of frames it takes to travel from 0-1, though I haven't tried it (in my current situation it's easier to keyframe it). But since this is effectively what a motion path
node does with "Use parameterization" turned off, it still doesn't make sense that simply plugging that to the subCurve max value doesn't yield that exact result.