I like it, but I don't like the name one bit. I would propose ::Simple, but that's already taken so I pondered a bit, and came up with Exporter::Tidy. I believe that would be a good name to describe your module's goal as well as its characteristics.

I agree it can coexist with Exporter::VA which is a nice module when you want its features - but I wouldn't want to be dragging its weight around for things like modules used in small CGI scripts. What I like about this module is how it takes care of the cases where one might be tempted to write one's own import.

As for configuration directives, it should be as simple as introducing a config => [] tag whose coderefs get called immediately, rather than exported. A bit of extra syntax to be able to pass parameters from the importing use might be good.

And finally, I'd like to see negations - being able to say f.ex use Module qw(:all !foo); to have all symbols but &foo imported.

Makeshifts last the longest.