Prefer the plugin when:
- the project already runs
pylintdirectly; - the configuration should live with the rest of the Pylint settings;
- the same invocation should work for local developers and CI.
Prefer the CLI wrapper when:
- the command line should make the shim behaviour explicit;
- a temporary PyPy lint run is needed without editing project configuration;
- the wrapper is easier to place into a CI job than a Pylint plugin setting.
Both paths call the same public install_patch(...) function, so their
patching behaviour is identical.