"Although BoringSSL is an open source project, it is not intended for general use, as OpenSSL is. We don't recommend that third parties depend upon it. Doing so is likely to be frustrating because there are no guarantees of API or ABI stability." (Their README).
> LibreSSL
That does indeed still seem like the most promising avenue. But it is "just" a fork of OpenSSL.
> rustls
... which relies on one of two crates with zero regard for long term support. "Latest release or bust" doesn't cut it for crypto.
Yes. Which is precisely why you need cryptographic libraries that take long term support seriously and don't just fix whatever the latest version is.
> Just recently you needed to block eMudhra intermediate certificates.
Why on earth is your TLS library responsible for your CA certificate database?!