Hacking Alexa LogC LUT to other footage?

I was very excited midday yesterday to see the headline about automatically getting LUTs on Alexa footage...assuming it would mean something good for all other camera shooting Log.

Very disappointed to find out that the functionality appears to be tied to metadata that only Alexa files would have, and that I can't seem to find a way using the metadata panels to force it onto other media.

Here's what I know:

-There is a metadata field called "Log Processing" that allows you to turn the LUT on or off for ONLY Alexa footage. This field isn't normally shown, but you can add it.

-Adding this metadata field to other views, and inspecting other media, this field will not display in the inspector, even though it is of the "Studio" metadata set, not "Arri"

-Assuming this means that somehow FCPX is looking for presence of another metadata field before it allows that field.

Given how it's implemented, it seems if I can find the right .plists or XMLs, it could probably be hacked onto other media. Doesn't seem like it would be hardcoded into the app.

Anybody got any ideas?

Okay, learned a couple things. If you add additional metadata to the QT files outside of FCPX, you can fool FCPX into reading as Alexa files and applying the LUT.

Arri Color Gamma SxS: LOG-C
Arri Look File Burned In: No

I can not find a way to batch add these fields though to QTs. Digital Rebellion's QT Edit can edit one file at a time, but I need batch.

Any other way to batch add metadata to QT's? It would be awesome if there was a way to force add inside FCPX.

Which camera are you wanting this for?

S-Log2 / SGamut from the F55

Tim Dashwood just or is just about to release Editor Essentials that has a De-log filter, which helps me out a lot, but now I'm greedy and want FCPX to do it for me automagically.

So, so close. I can't believe they got a framework to do this with any camera, and they just enable it for one. Gah.