As a workaround for this, you can use a traffic policy on the outbound interface to remark the packets as they leave the device. in this way packets will be processed by using the Dot1s locally and the DSCP priority will be changed according to the behaviour configured in the traffic policy.
traffic classifier Test
if-match 8021p 5
traffic behavior Test
remark dscp cs5 dscp code 40
remark 8021p 5 new 802.1p value
This behaviour is due to trusting Dot1s priorities. Once this happens DSCP priorities will not be processed on te local device. That is why it's imposible to use qos map-table for this kind of binding.