If course the P2P nature of the project means other people can find out exactly which of those resources you're looking at...
This sort of system helps against some sorts of snooping, but certainly not nation-state adversaries.
But these resources are probably already cached by the browser anyway (using the appropriate http headers). So how can this solution add any improvements to that, once the resources have been loaded for the first time?
I often using "private browsing" as a way to get another login session (e.g., login a test user while still having admin user logged in).
The obvious problem was that storing scripts locally got a bit out of control when considering having to store all versions.