I agree with Mark, creating a new movement class would allow more flexibility in what is hovercraft and what isn't. I also agree that this kind of modification has chances of breaking the whole code down...
That would even allow putting hover-units in the same buy list as non-hover ones if needed (I can't figure out where that could be needed except maybe if you want to collapse together hull- and hover-based landing crafts).