The answer to this is on page 36, in the general intro to Virtues & Flaws:
[i]"Flaws come in two broad types. General Flaws hinder the character, Personality and Story Flaws enhance stories. ...If a General Flaw will not hinder a character, it is not a Flaw, and the character should not be allowed to take it...
Some Flaws, such as Blind or Mute, could be easily fixed using Hermetic Magic. A character with easy access to such magic can only take such a Flaw if there is some reason why it cannot be fixed, such as that it is part of a character's Essential Nature (see P. 79). In general, characters cannot take flaws that will be quickly removed in play."[/i]
It's that simple.
So, if during CharGen a mage takes some physical Flaw and then whips up a quick fix for it, one that would make it difficult for the SG to imagine any reasonable situation where it would be a hindrance (or the SG is simply not interested in going through the narrative gymnastics to achieve that situation), then disallow it. If this occurs later, during game play, the best solution would be to rule that another Flaw must be taken to balance that lost flaw (similar to how defeated Enemies or a lost Animal Companion might be treated).
(And a wise SG would make this very clear from word one for new players, or players that they know tend to lean in that direction in other games.)
Removing Flaws is a houserule - you're welcome to go there, but there should be other rewards that your players would appreciate more (or simply balance those removals against undeniable new Flaws acquired during gameplay, such as new enemies or wounds, or anything else that fits the descriptioin).
While we're on the subject, it's also suggested in that same section that similar rules be applied to Story Flaws. If, for instance, a mage wants to take "Black Sheep" or "Close Family Ties", then the SG must see that as something that will add to the story, and the Player be agreeable that their mundane family will be a significant and meaningful factor to a mage's life - or it's not applicable.