Encapsulate table with view
Well,


A view increases the overhead but if the view only contains a select with a different column ordering, the overhead will not be noticeable.
You can also rebuild the table with the column order you want (a rather expensive one time operation) 
Most people agrees that views should follow the same naming standard as tables (i.e. no V_, or any other, special prefix)


Having said that, software should almost never do selects or inserts, without specifying the columns.