Hi @mfroehlich,
for projects bound to a SonarQube server, we think that SonarLint should enforce, as much as possible, the same ruleset as SonarQube, so that developers know that if SonarLint does not detect an issue while they code, there are good chances SonarQube will not raise new issues as well (although there are a few exceptions to this…)
Thus, at least in the short term, we do not plan to add the possibility for a rule to be only activated in SonarQube but not in SonarLint for projects bound to a SonarQube server.
On the other hand, we understand that some rules may create noise as they are already built-in in the IDE itself - so for projects that are not bound to SQ, we may review whether certain rules should be activated by default or not.
Thanks for the above valuable feedback, we are going to keep this thread open to gather feedback and votes from more community users.