This is where I would suggest altering the format that HPT and EFI Live use since you are not making multiple versions of the same OS....unless of course you planned to make multiple versions of the same with various option sets.Based on everyone else saying the same thing I think a new OS number is in need. The next question is what should it be?
When most people refer to an OS number they use the last 4 digits since they the unique values that separate many of the OS's. For example you have the 2156 OS and the 6125 OS. I think it would also be wise to include a version number as part of the OS number similar to the way software does as it would make it easy for people to know if they are using the current version of the OS or not. So you could do something like 21560001, where 1 is your version number. It makes it easily identifiable as to what it is based on while also making it easy to tell what version of the OS is being used. Of course this is simply a suggestion that would keep it simple.
I would agree you have taken it much further then any one else and that in it self is very impressive. The danger is that tuner pro does not validate that an XDF is being used with the correct OS number bin file making it very easy for someone to apply the patch onto any file they like and corrupting it in the process....making it also very dangerous.TunerPro seems like the only software that had the ability to patch like this. I feel like this is what it was made for, but I just took it a little further than most people.
A stand alone program would be something for useful for distribution if you anticipate releasing additional OS's or wanted to create varying levels of patches, for example allowing the user to decide if they wanted a 2 bar version or a 3.5 bar version. However if you planned to release these and do not plan to create additional features or versions than simply distributing a bin file would be all anyone would need and is how both HPT and EFI Live both do it in a manner of speaking. They both require flashing the custom OS into the PCM and then reflashing the PCM with the calibration data.That all sounds great, but out of my realm of knowledge.
There are at least 4 people that have posted in this thread(and 2 people watching it) that are all capable(and likely willing) to write you a simple program that would validate the OS number apply the patch and correct the checksums. What it would really come down to is what format you currently have the patch data stored in and what would be the simplest way for you to supply that data into a program so it was able to create the patch. When you say you wrote the patch in Google Sheets, do you mean spread sheets or was it a data base? If you used a spread sheet, with a columns for starting and ending addressing and then the data that was to be inserted over that range I think it would be pretty simple to make a program read that and create a patch from it. But that's just some speculation as to how you've formatted the data.As awesome as that would be sadly I'm surprised I got as far as I did. I mean I wrote this patch in google sheets lol, so I don't think I'll be able to create an application like that.
Given what the EPA is doing in the US and the way they are cracking down on things this would actually be a terrible idea and put PCM Hammer in a potentially dangerous spot drawing attention from the EPA. While the EPA them selves may not notice it, there are US based companies that are watching both PCM Hammer and Ls Droid who would be more then happy to inform the EPA about it and start pointing fingers.Quick thought....what if the patch was a part of PCM Hammer?
As far as having support with commercial tuning software, as someone else said, it is very possible EFI Live would add support for this once its been used for a bit and proven its desirable. I would also imagine it would be very easy to get Tuner Cats to add support for this as well and Cats may even welcome the idea since they do not have support for any COS's. It's also almost guaranteed that at least part of what you've created is also going to find its way into Hp Tuners since they have support for most of the EFI Live COS's at this point and have shown they don't care.