Nobody in the industry will even take notice that this exists. If they do accidentally come across it, far from being scared or "taking notice," it would at best circulate around a few internal email lists to give everyone a good laugh.
In fact, it wouldn't surprise me if this was actually developed by an ad network as a joke--they know that ad-block users aren't going to be making them any money anyway, so why not put them to use as what would essentially amount to a free bot network of very natural-looking traffic to send to their advertisers? Sure, it might lower conversion rates by a fraction of a fraction of a percent, but any amount of natural-looking traffic coming through to advertisers that isn't obvious bot traffic only increases the perceived quality of the ad network. It's much easier to shuffle the blame for poor conversion rates off to the advertiser themselves than it is to explain away low traffic volume or bot clicks.
Bot traffic is usually pretty easy to identify--very low quality traffic all coming from the same block of IPs, geographical region, or publisher. The quality is basically a measure of conversion rate for that subset of traffic compared against the average conversion rate across the entire network. In the (unlikely) event that something like this product catches on and sees a high enough adoption rate to actually affect the numbers across entire ad networks, it would lower traffic quality equally across the board, thus making it essentially undetectable. It's when that starts to happen that advertisers and publishers start to get desperate and we start seeing them play new and shadier games. You might be happy and safe behind your ad-clicking blocker, but grandma and gramps who don't have the technical know-how to protect themselves will start to see new fake download button ads, pop-unders, auto-playing video ads, and other gross tactics being used to try to compensate.
My time in the industry has pretty heavily biased me against online advertising quite a bit (I run ad blockers, no-referrer, strict whitelist-only cookie policies, etc), but I can definitely say that running this extension is pretty antithetical to its stated intention.