Sorry for the slow response; I was away for the end-of-year holidays. The answer to your question requires some explanation.
My flight plans are for sightseeing with low, slow ultralight aircraft. Takeoff, see a point of interest, and land. A user loads the flight plan and then follows on-screen visual markers. The directional markers have labels like “Turn left here”, “Bear left to land”, “Descend and follow the river”, etc. So, I am not using waypoints in the traditional way, but rather as on-screen road signs.
MSFS waypoints are not compatible with low, slow sightseeing flight plans. MSFS uses a variety of factors to predict upcoming turns and it dynamically controls the display (and suppression) of waypoints. My plans require waypoints to behave more like custom points of interest rather than as GPS waypoints. I have developed techniques that overcome MSFS behavior to provide accurate, persistent tips for creating low, slow flight plans.
These plans do not work if MSFS is allowed to control the flight and override the plan. Thus, the plans provide instructions to avoid any copilot, autopilot or ATC engagement. These are short, stick-and-rudder flights.
Unfortunately, MSFS still finds ways to override my efforts. For example, in a totally manual flight, the next on-screen waypoint may be, “Turn left here.” On the way to that marker, the marker disappears and a directional marker pops up, pointing back to the previous marker, and it is persistent. It is a u-turn.