Is this something many hosts could do and is it desirable?
1) The transform matrix -
to complement this - would be cool if we somehow could access inertial sensor motion data even if not a lot of normal camera spit that out yet (aside phone cameras - latest goPro, garmin, and other action cameras and some video dash cams do spit out relevant data).
Already difficulty one - it's a motion matrix or a normal spatial transform matrix, is the source fisheye, rectilinear or equirectangular... is it a 2D matrix, a 3D matrix, a projection matrix? (3x3,4x4,...).
2) In general I like suite format for revision purposes (so #define don't need to be versioned themselves).
3) Image Pixel Transform - shouldn't that reside in multi-channel image model? I am worried of too many image callback buried in different places personally.
This link is interesting (although in domain of scripting)