Model separate Person types as separate tables at beginning of application's lifetime?
My gut feeling (which seems to be borne out somewhat by this question) is that you should go ahead and do different tables, since you can always migrate later to a schema where these different Persons all have the same kind of Account associated 1:1 (as suggested in this answer).