ACME post-renewal hook to fix TLSA records of jumping intermediate certs

Hey there,

Sometimes Let’s Encrypt appears to randomly switch between its intermediate certs

Let's Encrypt Community Support

Force use of R10 or R11 intermediate CA

Is complaining to the vendor/developer of this software not an option?

Since Let’s Encrypt does not support the selection of the intermediate cert, I see only one possible solutions:
Use a post-renewal hook to automatically update the TLSA record. However, I haven’t found any hooks exposed.

Do I need to modify the Dockerfile to introduce the hook into acme.sh myself or is there another way?
Are there other possible solutions for the problem?

Thanks,
neodym