If an ErrorMessage is sent to an outbound channel adapter, and the message contains an AMQP_RAW_MESSAGE header, republish the message in a similar manner to the Spring AMQP RepublishMessageRecoverer including exception information in headers.
Then, adding an outbound adapter can be seamlessly subscribed to the inbound endpoint error channel to get republish to DLQ behavior.
This will likely need a minor change in Spring AMQP to move the X_* headers from the recoverer to a utility class. Although, they are public so maybe it's ok to leave them there. On the other hand, they should probably become first class properties of MessageProperties.