in your first pic it looks like the AFTER isn't high enough and if you had run collision detection it should have flagged this. as far as you original question, I tried replicating it on my version (2021.2 CAD++) and while the B/A values were sometimes generated different, when I adjusted them to be the same, they were the same.
1.) vpt.se wants to express that with his cone the safety movement starts incrementally from the last measuring point instead
of, as usual, from the zero point of the cone.
2.) I don't do collision detection with existing programs, maybe it is suddenly different (maybe software update)
vpt.se I think we have just fixed this issue in 2023.1#57 and up. I was in lab this week for online testing and have taken a tour also on that functionality.
If you can get a chance for testing in the next available installer, to confirm it's working as wanted, that would be appreciated. Thanks and happy weekend.