Dynamic renewal timing

Hello,
We are using several CAs with different profiles. As a result, the validity periods of the certificates vary (6–365 days), meaning that a general configuration in days is not sufficient. In addition, the validity periods of the certificates will be shortened in the near future, meaning that a configuration in days that is suitable today will no longer be suitable tomorrow – and so the configuration would have to be adjusted despite automation.
Let's Encrypt recommends renewing certificates after about 2/3 of their term. This works for both 6-day and 365-day terms today, and it will also work if the terms are adjusted automatically.
Would it be possible to include such a configuration option?
Thank you!
Best regards
tw-

The issue mentions no files, tests, or entry points. Start by locating the renewal timing configuration and the code that determines certificate validity or renewal eligibility; done means supporting a validity-period-based renewal threshold that works across the requested certificate lifetimes.

Written by the indexing model from the issue text.