So, the feedback on the rejection was related to how cache was being used and mainly around the fact that running the support tool will clear that cache (to be expected)
So, with that in mind, I'm going all-in on storing the translations in the database instead. And with that, I'm going to build in some functionality that will allow you to refine the API-provided translations by editing them in the ACP (if that is something you wish to do) - I have a few ideas around how that is done, which I am working on over the next few days.
Once done, it will be v1.2.0 that will be the version release - and I'll update here once it is released, along with the 'sale' details that will be in place initially.