Certbot should complain about already having a cert for that exact set of names.
You would have to include either --force-renewal to force the renewal even though it is not due to be renewed. Or it can also be forced to create a new additional cert with the same names (then having two certs covering the same names - but that wouldn't meet your goal.)
That said, I don't really think your goal/plan is foolproof.
There are many reasons that could inevitably regroup them.
Like: Any type of outage would force certbot to retry twice a day for that cert until it gets renewed.
What happens when it tries for longer than the difference between that cert and the next?
[they get combined into the following try - and it will try renewing them both on the same run]
I think what you need is an --only-renew-one-cert-per-run
or an --immediately-stop-after-deploy-hook-call
parameter to get your plan to always work.
However, it shouldn’t be necessary to interpret stuff, as it leaves room for interpretation errors. The documentation might need a little bit more clarification.
I think language is probably the biggest hinderance on correct interpretation (especially with the written word; as found here).
…there will always exist someone who will misunderstand what someone else wrote…
I’m all for improving things; but I don’t see a clear way to remove the vague ambiguity, nor the return on the time investment it would require… We would better serve more people by putting efforts into having all docs translated into as many different languages (than into trying to perfect any one single language documentation).
[barring any obviously required corrections/updates/changes]
Maybe there exists some room for improvement in this section; but can only see some when read only in part…
When read in whole (the entire paragraph) it seems unmistakably clear to me.
Disclaimer: I’m far from the typical “target” audience/reader.