What we've done for now is add the needed context from the
wrapper manually to our ruby executable that we would like to wrap
and then using no-wrappers (this is an internally-used gem so not
an issue for us to make that restriction).
I can see where the multi-versions would complicate things, but
in practice I think the restriction is reasonable (and for an
executable that needs it, it probably always will in practice so
backward-compatibility might be a problem).