Yes, that is a modern additional feature to consider: Store configuration in a database (could even be user-specific!); you could reduce the .inifile to holding the database connection information.

But I wouldn't hard-code anything in the .pmwithout a very specific and strong argument to do so.

The benefits of keeping code and data separate is a very, very long list, and I've probably forgotten more reasons that some people will learn. Don't make your people edit .pmfiles just to make a config change. You are likely to live to regret it if you do.  :-)