What would be the alternative? No linter at all, and thus no style fixes at all - except for the ones found during code reviews. But obviously - the latter have to be applied manually as well.
So this ultimately depends on how much value you see in those suggested style fixes the tool provides, and if you think applying those fixes (manually) is worth the hassle in the eyes of you and your team, or not. It also depends if there exist an alternative tool which may give you more "bang for the buck" in return and can apply automatic fixes (but let us assume this is not the case).
It could also be a learning process - ideally, after using such a linter some time, you will try to avoid to break its rules first hand, without a significant loss in coding speed.
If that's not working for you, another approach could be to use only a subset of the linter's rules, and keep only the rules where you see the most value for you and the team. If that is not possible "out-of-the-box" - well, this specific linter is open source under MIT license, so it may be possible for you to extend / modify the tool to allow more finegrained configuration options, or to disable some things you don't like. If you want to, and have some time to spare, you could even try to add some "automatic fixing feature" by yourself.