Yes. My design approach was that the path planner would only be run when starting a new trajectory. If any planning variables are changed mid-stream, the entire path needs to be replanned, which has certain consequences. Logically, we should redo the entire path, including the waypoints we have already visited, and then start over again at the beginning. If we don't want to start over, then a new path would be necessary, which includes only the future waypoints. But at this point, we're starting a new path plan anyway, since we have a new path, and thus it doesn't matter if we update the variables or not.

The above is true for the current path planners. If in the future there were some kind of adaptive path planner which required interaction with a ```FooBar``` field delivered over the telemetry link, then it would be reasonable to run ```PathPlannerSettingsFooBadGet(&pathPlannerSettingFooBar)``` inside that particular path planner.

Of course, this can be changed to simply be a callback, but it didn't seem worth the overhead since the settings object is only necessary when initializing a new path.