Last I looked, BoringSSL[1] was a drop-in replacement for 1.1, as long as:
1. Your usecases intersect with Google's (they removed bunch of stuff during the initial forking phase).
2. You can handle the following:
> 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.