Which complications would those be?
ResolveSubresource(), which I think we would also need in D3D12. It can be done but do we need it?
Well, get_resource_readback_with_command_list_and_states() already handles multi-sampled readback for d3d12, so that part should be fine. It doesn't seem especially complicated to add to the d3d11 runner either?