ESLint alternatives that are not Prettier for a React Native project

I have been analyzing the performance overhead of various developer tooling in cloud-based CI/CD environments, and the resource consumption of ESLint, particularly in large React Native monorepos, often translates directly to increased compute costs. While Prettier is the common suggestion for a formatting-only alternative, its stylistic rigidity is not always suitable for teams with established, nuanced code style guides.

I am seeking a linter focused purely on code quality and potential errors, leaving formatting concerns entirely aside. The goal is to reduce the static analysis load during local development and in the pipeline, which can lower the EC2 or GCP Compute Engine time for CI jobs.

For my current context:
- **Editor:** VS Code on macOS (Apple Silicon)
- **Project:** React Native with TypeScript
- **Key Concern:** ESLint, especially with the `@typescript-eslint` plugin and Airbnb config, shows significant memory usage in the language server, impacting startup.

What are the viable, maintained alternatives? I have evaluated:
- **Rome (now Biome):** Promising, but its bundled formatter is a core component and cannot be fully disabled, making it a Prettier-like replacement.
- **Oxc:** Extremely fast, but its current linting rule set is limited compared to ESLint's ecosystem.
- **Static Analysis Tools (like SonarJS):** Often too heavy and not integrated for real-time editor feedback.

Is anyone successfully using a minimal, performant linter for React Native/TypeScript that focuses solely on logical errors and anti-patterns, not formatting? Configurations and observed performance impact on your development environment would be particularly valuable.

Optimize or die.