Forwarding back to d3dx10 seems questionable. There was an idea to have a shared wine-specific module that would carry all or most of d3dx bits.
There was, but it's not clear it's necessary in this case, when it's possible to simply forward one export to another. We already forward all the other d3dx10 methods to d3dx10_43, and I'm not aware of a reason not to do that for d3dx11 as well.