It appears that Dash uses the "attacker economist" approach.
I happened to read the quote, but what exactly are you referring to? What part of DASH implementation uses it and what sub-type of attacker economist logic is used?
Here is another quote of exactly what I am getting at in reference to DASH:
In other words, instead of purposely designing their systems to be cryptographically sound so that the "attacker will definitely fail" or the "attacker will probably fail", they instead (unwittingly?) design it so that "the attacker's expected cost of carrying out an attack exceeds the attacker's expected benefit from doing so."
The unfortunate knock-on effect is that such an approach only works like that for a limited time...as the value of the cryptocurrency grows, so does the level of sophistication of the attackers that find it an interesting target.
Trying to solve the privacy problems in a way that relies on the honesty and opsec of a small group of individuals is simply privacy theatre, no different from those that claim that Bitcoin is private as long as there's no address reuse.