Are you planning to integrate profiles into code? I don't use dngs, because they additionally slow down the camera, but I think it would be good to put them into some folder on SD card, separately from the code, so users can change profiles without rebuilding the code. These profiles could be universal - contain only color matrices (one or both), like now, or forward matrices also, or also some of lookup tables like your profile
Anyway, I don't see a big advantage of having profile embedded in a dng. Only ACR and LR work with these profiles, and if you have them installed on the computer, it's easy to put appropriate profiles also. But maybe someone else will find it useful, it's up to personal taste
As about profile you attached, a took a brief look. So, in comparison with various profiles provided by Adobe, where difference between CM1 and CM2 is relatively small (in terms of position of primary colors in xy diagram), your profile has position of blue primary in daylight matrix very far outside xy diagram (while its position in tungsten matrix look quite ok). That's why blue colors are much more saturated. I tried it with my A650 (different sensor, but similar pixel size, so colors using As shot WB are quite good) and most real life colors including blue look quite ok, only very saturated blue on my test images are way oversaturated and too dark, so that result is even outside PhotoPro color space, although scene color is inside sRGB. Can't be different no matter which sensor, because of position of blue primary in that color matrix. But don't worry, even profiles provided by Adobe are faulty in blue range - there are currently only two sets of very last profiles (for 550D and D3) where they took the right approach (well, one thing still needs to be addressed), using only conversion with very big lookup table (90x16x16) and without matrix operation (in fact, with dummy forward matrix).
Real thing would be making a tool that would produce these profiles out of the camera. Idea is like this: put a special custom made CHDK raw file on SD card and develop it to jpeg using CHDK function. Then, comparing output and input, calculate a lookup table in the profile. Maybe I'll do this somewhere in the far future. I'm currently working on a calibration program for my 400D, because Camera profiles for 400D from Adobe are not very acurate, job is almost finished, so I have most of the code for this job, only time to finish this and my enthusiasm is running out ... Tried DNG profile editor first, but it's intended only to do slight modifications on existing profiles for existing cameras - it's useless if you want result that looks identical (or almost) to jpeg from camera (if that is the goal, of course)
