I hear where you are comming from regarding the current state of FTM and data entry. If I was only a FTM user I would probably follow your process as well, not because you are doing it but because it is the only possibility with FTM.
However, this thread is more geared toward the thought that if FTM is changing to make AKA a full name with surname, given name etc. This is not a good design decision not just from a GEDCOM view but from a database view. Having two field both representing a name but stored differently is very troubling.
Then putting GEDCOM on top of that, I still can't import my very large database with compliant GEDCOM. I spent a lot of time when I moved off my two previous software packages (Generations and PAF) dropping the stand alone AKA and married name fields to using recurring name tags, now to loose them when I import into FTM is very wrong.
This is just one of the many design decisions FTM made that were probably based on the wrong people driving the process.