Ahh, I hadn't been using the -force64 flag. Results:
I tried entering each line in one at a time and then hitting enter (and when I did that the commands corrected me on syntax or terminal told me the files didn't exist or that it couldn't run binaries)
Then I tried entering the commands back to back and that of course didn't work.
Then I entered commands in the way terminal was saying to (like amd_insn_patcher /usr/lib/libSystem.B.dylib /usr/lib/libSystem.B.dylib.patched and then hitting enter) and when I tried to do amd_insn_patcher /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore.patched Terminal output Illegal instruction to every command I entered and no apps would launch in finder. I would have saved what my terminal looked like exactly but Textedit froze while I was saving, and then Terminal froze when I was saving the output.
All of the lines were input in the order of the first post.
What I'm going go try now (and I'm typing this while I wait about 20 minutes for it to finish) is making 2 copies of my backup partition that I've been restoring from (using GParted if you're curious), have the amd_insn_patcher modify files on the drive that hasn't been booted, and then copy the modified files over to the active partition, that way I can at least patch all of the files before OS X destabilizes.
I'll post back after I try it, either with good news that it worked or begging for more help
