In principle, it works with any app that can be convinced to run arbitrary code by changing its resources. What Safari is doing isn't wrong and wouldn't cause an issue if TCC would check the entire app, including resources.
It's true that you can't use this to copy the privileges of _any_ app, only of those that have this property.
It is limiting the scope very much. TCC shouldnt check entire app for signature.
Safari should verify its resources, is what I am saying
I guess any Electron apps and apps using webview for its local resources do it too.
Basically if you can do with any app, it is OSX, otherwise apps fault
Even apple guides state:
You must also verify that the file you intend to read from or write to is the same file that you created.