Earlier quoted context omitted.
You don't understand how this works. Firefox just provides some APIs that the DRM blob can use. All the decryption is done by the blob, not Firefox. You can reverse engineer the blob itself to an extent, but that will also become impossible with SGX (hence 4k on kabylake + edge only).
What's to stop someone reverse engineering the blob before it's loaded into an SGX enclave? I don't understand it very well so I could be missing something, but wouldn't that at least let someone document how the DRM works even if not running their own implementation?
The "someone" in your hypothetical can modify the blob, but then they won't be able to resign the blob, so SGX will fail to load it.