This is a good idea. If you see areas where this can be done can you file a JIRA (or better yet open a PR)?
Will start to get some PRs in - I think the executors are the hardest change but will start with these as I find them.
In this case I think we should get rid of the Netty one entirely, and just have an agnostic one.
+1 I think once we have agnostic alternatives remove the Netty specifics from Undertow 3.
Maybe we also need an Undertow 2.1 branch, which will aim to improve compatibility by adding methods like this that will work in both versions.
What is the policy regarding adding new API in 2.0 if this approach needs a minor version increment may be useful to get something started.