Nope... it doesn't work that way. Think of the hex string you place in the com.apple.Boot.plist file as a sort of road map within your PC. It has to know where to start, the routes through your MOBO and then where to end... so you see, it is completely dependent on an individuals system to create this for themselves. I'll give you a good example of why you need to do this every time you might install the OS:
I've been working with OSx86 for a while now and have "redone" my machines many many times, but I decided to save my "fixes" for faster rebuild times, however the hex string in that file barely ever (if at all... can't remember if it did at all, but I'll say "if" just in case) matched up and I had to redo it for the present system each time.

ATIinject is a kernel extension that isn't like EFI at all. With an EFI string you are dealing on a much simpler code base (hexidecimal... right around assembly code in a computer) than a kext which deals with Device IDs. These are simple to look at but more complex because of what they mean. A Device ID shows a previous knowledge of the system being located somewhere else and thus can be moved from computer to computer to allow others to have the same fix.

Hope that makes sense... its late here and I'm tired now. Off to bed.

Cheers.

---