Best practice for "unexpected white balance coefficients" in darktable

In 2018 I did a bit of experimentation with using the camera color profile to correct white balance. Easy enough, just don’t white balance the Colorchecker target shot, make the profile, and apply - ta-da, both gamut is compressed and white balance corrected, what’s not to like? Here’s a link to the post of my two comparison images:

https://discuss.pixls.us/t/gimp-2-10-6-out-of-range-rgb-values-from-cr2-file/9532/192

At the time, I thought the white balance from the profile looked better, but now I don’t think so. The green hues are better-separated from their adjacent yellow ones in the separate color profile/white balance rendition.

I never took up the method in practice, seemed to be too much trouble for the “improvement”. Still, the application of white balance in a chromatic operation still just seems less-destructive than those rather harsh channel multipliers; makes me want to compile my darktable master and play with the new tool…