Your first link has very different errors to the ones you're experiencing, and although the SFCFix tool they may have used in the second has evolved a lot in the past year, I don't think it deals with this type of problem. I've brought the errors to the attention of the tool's team, so hopefully I'll get some good advice from them.
As for the Payload file error that you have, CheckSUR only does a partial scan of the system, and SFC often picks up more errors (and give more detail on them anyhow)
Oddly, in this case, it only picks up one error.
Code:
Line 110088: 2014-09-07 18:49:39, Info CSI 000003df [SR] Repairing 1 components
Line 110089: 2014-09-07 18:49:39, Info CSI 000003e0 [SR] Beginning Verify and Repair transaction
Line 110092: 2014-09-07 18:49:39, Info CSI 000003e2 [SR] Cannot repair member file [l:24{12}]"usbvideo.inf" of usbvideo.inf, Version = 6.1.7600.16543, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
Line 110095: 2014-09-07 18:49:39, Info CSI 000003e4 [SR] Cannot repair member file [l:24{12}]"usbvideo.inf" of usbvideo.inf, Version = 6.1.7600.16543, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
Line 110096: 2014-09-07 18:49:39, Info CSI 000003e5 [SR] This component was referenced by [l:150{75}]"Package_2_for_KB979538~31bf3856ad364e35~amd64~~6.1.1.0.979538-4_neutral_GDR"
Line 110101: 2014-09-07 18:49:39, Info CSI 000003e7 [SR] Repair complete
This makes me suspect that the CheckSUR Payload results are false-positives - possibly a result of the registry failures.