This is where the people making the blocklists get stuck. Marcus Aurelius, ad block developer, decides that the deck ads aren't that annoying, don't break the page they're on, are low bandwidth, don't track you, etc. And so MA leaves them out of the list. But everyday he gets 100 bug reports "I still see ads!!!" from users who never want to see a single advertisement on any site ever. What's MA going to do? Probably give up.
Just ask the user on first execution if small ads that don't use a lot of bandwidth and that don't track the user should be allowed and leave that as an option in settings. The app could also provide a link to an example site for the user to see what the ad would look like. With iOS 9, it's also easier for the user to get back to the application after viewing the example site/page.
I do commend Deck ads for having no cookies, no JavaScript, no counting clicks, etc. It's not a model for the entire web since many marketers want insights and statistics on users, but it definitely works quite well and is used on several popular sites.
The architecture of iOS content blockers seems not to allow that. No information is allowed to flow from safari to the ad block app (to allay concerns that the app itself is spying on you).