The problem is just this: clients cannot ignore only your tagged kinds 1, so you are creating noise in all plain kind:1 apps to take advantage of free visibility, and actually trying to force support.
A better approach would be to support kind:9041 and work together with clients devs to support it more extensively.

What is that "social proof use case"? 

 Appreciate the feedback. Social proof use case is pretty self explanatory. 

 Sorry, maybe it's my fault, but it's not self-explanatory enough for me.
Are you talking about 'social proof' in supporting the pubpay tag by devs, or some other end-user related dynamic?