The Sion instrument approaches as an example use many local fixes that are hard to program in by eye and their Aerofly generated names cannot be edited to match published names. If they could be saved then typing in the position would be a one-off task which would be more popular than one might think.
Not even using the Aerofly FAF at this time as a 2,000 ft/10 miles-through-the-mountains solution, would be easier if the published fix altitudes could be entered and associated with the fix on the flight plan page, even if they are visual only and not followed by a 3D auto-flight sim’ approach. Vertical speed mode control is used in following the non glideslope procedures anyway.
Perhaps assumed user adherence to the 3D auto-flight sim’ approach feature stifles flexibility?