Upon re-reading, it's perfectly clear that your Config.pm is a data store... the lack of clarity was all on my end.

I have a possibly irrational aversion to allowing modules to pollute my namespace, so were it mine to do I'd subclass Config.pm to provide an interface layer and work toward phasing out the legacy version over time.