PSShouldProcess Rule and module specific adaption

Scenario

One of the default rules checks, whether a command that supports should process, actually uses ...

$PSCmdlet.ShouldProcess( ... )

Now, this is a great rule in principle, but in the framework module I maintain (https://psframework.org) I've got a cmdlet that replaces that method call (for readability and mocking reasons).

My current solution is to disable the specific script analyzer rule (PSShouldProcess) in my automatic tests. Which works well enough for my purposes.
But it would be more awesome if it were to detect the command and equate it with the method call (cause I'd actually appreciate having that check enabled, if it were practical).

Creating my own rule wouldn't be a problem, so my own projects would be covered. But since I'm trying to distribute this to others - with increasing success - distributing the custom rule to their tests would be ... inconvenient outside of PSScriptAnalyzer.

Questions

What's the policy on changes to rules that are module specific?

If I write that update, would it even be considered?

Beginne mit der PSShouldProcess-Regel und den im Issue beschriebenen automatischen Tests; keine Quelldatei oder kein Testpfad ist genannt. Erledigt wäre dies mit einer konkreten Richtlinie für modulspezifische Befehlsäquivalente und einem vereinbarten Implementierungsumfang, gefolgt von Tests, die zeigen, dass die Regel die vorgeschlagene Anpassung verarbeitet.