We have this requirements for our customers who were not able to has a direct bi-directional connection between DMZ (with potential API Gateway) and Corporate network (where other services placement) and suggest partner to build your own API "proxy" solution based on Fuse, EAP and AMQ Broker on OpenShift. This is a little bit overloading API GW features, but very desirable feature for many customers as other solutions requires to spend a large number of resources (money, software, hardware, etc.) for implementation rather then OOB solution.

Some quick analysis:
AsyncAPI specification description - AsyncAPI
Right now no Lua based clients for AMQP 1.0 (except old project for AMQP 0.9.1 - amqp - LuaRocks ) and it's difficult to embed this inside apicast functionality as custom policy or OOB.
Lua implementation for MQTT v 3.1.1 is available https://luarocks.org/modules/yongke/luamqttc