The problem with dcomp is that while adding stubs is enough to make some games happy, it's not good enough for upstream. After you add the stubs, other applications will start calling those stub functions, and more methods will be needed.
Darn, I was thinking a bit about this. Would it be feasible to have some implementation behind a feature flag, or some similar construct? That way applications checking, but not really using dcomp (...Dorico, at least) could function, without affecting applications and games outside that wineprefix.
For what it's worth, I have a slightly better version of dcomp at \[...\]
Thanks for the link! Looks like that implementation is indeed further than this blob of stubs. I'll have to try that branch out later today. I probably can't help develop that further since I don't really know a lot about any related topic. If there's some trivial changes that would help my use case, do you want patches? -- https://gitlab.winehq.org/wine/wine/-/merge_requests/9839#note_126237