I've had a look at the comments on BdJ.

I particularly noticed the one about hiding business info.
I don't know if there might be some value in hiding components on the program - I very much doubt there being many users who use them all but the business side (contacts/resources & etc) does speak to a particular design philosophy and purpose which was a big thing when Do-Org started. But times have moved on and most of this use has now moved online - into the cloud or corporate servers - even for SMEs.
Personally I see little need for hiding. An unused component doesn't really get in the way.
But I do see a lot of potentially usable functionality that I don't use because the database items are hard-coded. This is the sort of thing I was talking about when I was looking at the possibility of repurposing with the language options when they come.

I agree that I see no problem with unused Contacts or any other component.

What I do see is an opportunity to use Resources (or indeed Contacts) in a different way by having the ability to change the labels.

If it is true localisation, I would expect all visible labels to be changeable to the new language - eg in Resources, Product, Short desc, Contact name etc, should be changeable to words that are similarly meaningful in the new language.
Is this not what you intend?

That's fine. It means that repurposing will be entirely feasible.

For instance, not that I'd thought of doing it, it would be possible for someone playing a RPG (or running a game) to redo the Contacts to contain characters, possessions etc. Or details of the animals if they are running an animal sanctuary. I doubt if many people will be doing a query on an exported database, but they might be motivated to adapt a module if they have a particular need and have no use for the module's original purpose.