Well, the CV table was given so that users could truly tune their CV behavior. For that it works really well and just as intended. But it would take a lot of testing and just plain work to optimize it. Some did it but most want something that will get them a lot closer a lot faster and easier.
It just uses accel of the included axis motors to determine the worst case. This is why when designing a machine, it's good to have as much accel as possible and that all axes can run at the same accel rate without issue. Without issue being the most important part. Knowing accel you can calculate bend radius at any speed. Knowing that radius you can then calculate the max distance from corner it would be at that speed for each angle. Naturally it does not take any machine design flaws (flex, backlash, etc.) into account so again, best to eliminate those in machine design.
Most machine to a tolerance. +/- .010 for example. They want to run the path as fast as possible while staying within tolerance. That was the whole idea of the wizard. Increasing the tolerance will decrease the run time and make it smoother but keep the path within the given tolerance. Unless something (like backlash or flex) lets it exceed the tolerance.
Thanks!