It already does most of what you want and has support for native epoll transport.
I'm not sure what led Vert.X to be discarded, maybe not a Java shop? But we've used it extremely successfully for high performance REST and I know of several high profile tech companies that swear by it.
There's nothing I know of that compares with Vert.X in performance, stability, and popular adoption
While the bandwidth benchmarks are fun to see and write blog posts about, we also care a lot about keeping tail latency at or below 2ms than we do about getting more bandwidth at this point.
Still, those issues and not being a Java shop makes Vert.X/Netty likely a bad fit.
Thanks for replying with a well thought out response!
1 - See httpbeast in the latest round of the Techempower benchmarks: https://www.techempower.com/benchmarks/#section=data-r17&hw=...
Also why is evey immature native language considered, but the two speed demon languages without garbage collection - ISPC and C++ - are nowhere to be found?