Check the “TIFF and reference data” link over in this post in the Backlight thread. The “argyll steps.txt” file has everything you need. One command to read/compare your scan of the calibration target with the calibration data supplied by the manufacturer. Then, another command to generate an ICC profile from it.
With an ICC profile in hand you can do lots of things. It’s usable directly in places like Photoshop where you can simply “assign” the image to use that profile. But it can also be used to generate the kind of LUT that Resolve likes. So your first node would be to use that LUT and you’d be starting with the nice, “real” calibrated results for all your footage.
That thing is wild! Anytime you add “NIST-traceable” to a product description, the price gets another zero or two. But having 98 spectral response data points at 5nm increments for each color patch is awesome. I don’t know what I’d do with it… but it’s awesome. 
I’ve noticed the same throughline across all my hobbies: metrology. For whatever reason, I seem to love precise measurements and quantifying anything I can get my hands on. 
There’s something to be said here for why we calibrate monitors, scanners, and printers in the first place. Each one is a little different. And they drift over time. I generally distrust every “out of the box” state my devices arrive in. (This probably dovetails into my statement about metrology just now. I can’t turn it off in my brain! 
)
Agreed.
Alright, I’ll point the greywhitebalancecolourcard people at this thread and mention that there’s at least a little interest in them maybe making more than one at the smaller size.