zlib-ng for websocket permessage-deflate?

In a prior issue, [I was asking about using a system zlib](https://github.com/boostorg/beast/issues/2921), or boost::iostreams when the motivating example was CVE tracking.

I'm working on a piece of code now that consumes a really large amount of compressed websocket messages, and spends a large amount of run time decompressing them in beast's zlib implementation according to `perf`.

This piece of code is performance sensitive, and I'd like to try using [zlib-ng](https://github.com/zlib-ng/zlib-ng) or [Cloudflare's fork](https://github.com/cloudflare/zlib) to see about speeding that up.

Is there any way to make a websocket connect with permessage deflate and then let the user supply the implementation?

The issue names no source files, tests, or entry points; start by locating Beast's WebSocket permessage-deflate and zlib integration. Compare how a user could supply zlib-ng or Cloudflare's fork, and consider the work done when a supported connection path and its verification are clear.

Written by the indexing model from the issue text.