Not really -- during the execution of the route block, the x/avp lists from tm are set in the core, so the new x/avps are stored directly in the transaction. This is used for failure_route as well and any issue should have been exposed for long time. Unless it was the case of creating a faked env inside a faked env that should be fixed by my last commit.
I looked at the kazoo code and I noticed that `kz_amqp_consumer_fire_event()` is using fake sip messages to execute event routes. Are those event routes creating xavps?