Taxonomy_CSV Import UX improvement ideas

I am just documenting these here as I encounter them in hopes of helping someone in the future and to propose some of these as enhancements. I'll be in Austin June 2014 if you want to sprint against them together?

File name dictates the singular imported Vocabulary name and sort of derives machine name (and subsequent path alias):
* Geographic Region.csv becomes "Geographic Region" with machine name geographic_regio1_128:
Preferred would make the machine name more 1:1 with the name. Super-preferred: Why not provide optional Name and Machine Name fields?
* Side note, see #2235539: Strip .txt off name of generated vocabulary for Taxonomy CSV Import to mimmic this same behavior for .csv.

Multiple vocabularies per file
* Currently, a single file provides a single vocabulary. Multiple vocabularies involve an additional trip to the CSV Import for each vocabulary.
* Preferred would be an option to provide all vocabularies and their term hierarchies into a single upload. The root level items would dictate Vocabulary names following the same rules as file name currently does.