Hello @bhantol, welcome to the community and thank you for your feedback.
I understand how the architecture might appear as “flawed” to someone new to the ecosystem and used to UNIX-style, CLI-first tools.
The analyzers available in SonarQube, SonarCloud and SonarLint started their lives as plugins for SonarQube (née Sonar), when it was marketed as an open platform for code quality.
Their tight integration within the 4 supported IDE families through SonarLint allows for a user experience that goes beyond what most linters offer - with detailed rule descriptions, explanation of complex issues through multiple locations, and synchronization with the server quality profile and settings in connected mode.
Said otherwise, the analyzers were never meant to be run as standalone products, but rather to power a larger ecosystem.
With SonarLint in the IDE to catch issues while you code, and branch analysis / PR decoration in SonarCloud or SonarQube, it seems that your project’s quality and security should be pretty well covered.
This is the developer experience currently offered by our ecosystem. It can be really powerful if you embrace it, and I understand that it can appear as frustrating if you don’t want to.