Here, I'll explain what I think it does so you can at least correct what I'm missing:
(1) User visits web site example.com and needs to get file foo.jpg from example.com.
(2) foo.jpg is available at some content delivery network, let's say Akamai.
(3) User's browser gets foo.jpg from Akamai.
(4) Akamai now knows the user's IP address, the Referer (example.com), and the user agent info (browser version, OS version, etc.)
So what does the Decentraleyes add-on do? I think it does the following:
First, this add-on apparently cuts out the Referer when the browser asks for foo.jpg, but Akamai would still get the IP address (and the user agent info unless the user is disguising that). With the IP address you've been tracked, so does this really help?
Second, this add-on apparently gives you a local copy of foo.jpg if it exists (i.e., a copy of foo.jpg already cached on your own computer). Well, the first copy of foo.jpg had to have come from somewhere (either example.com or Akamai), so you've already been tracked.
NOTE: I'm not criticizing the add-on at all! I'm just trying to understand it.