Elevation Data preflight check

Is it possible to add a preflight check button in the Flight Plan to give a warning if any part of the flight is below the elevation data?

Recently we had an issue where absolute altitude was accidentally used or somehow sent as the elevation data for a flight plan when relative should have been used. Luckily it did not result in a crash as the behavior was noticed and switched to manual mode, however, is it possible to add a preflight check or warning if mission planner notices something like this? Also, maybe any other warnings for things that could result in mission failure?
This was on ArduPlane, although the preflight check button could benefit the copter firmware as well.

Some things it could check, elevation graph data vs. flight plan, minimum speed requested during flight plan vs. stall values, maximum pitch angle changes, landing pattern pitch changes, and any other critical flight plan settings that could result in mission failure if not confirmed by the user.

Start by reviewing Mission Planner's Flight Plan workflow and the elevation graph data described in the issue. Clarify which preflight checks are in scope, beginning with relative-versus-absolute elevation mismatches, and identify how the warning should be triggered and presented. Done should include confirmed checks for the agreed failure conditions and user-visible warnings.

Written by the indexing model from the issue text.