Would you implement markdown linter in your project and if so why?

I'm a fan of having a unified code across all team members in the project. Personally, this gives me the comfort of expecting the same way of structuring the files in the whole project which finally help in a quicker understanding of the code. For programmers, it is also easy to imagine and apply for programming languages like Java, Go, JavaScript, etc., where you have a linter which keeps. I introduced a prototype remark-lint as the standard way of writing all markdown files, although my colleagues at work have difficulties to understand the benefits of linting Markdown files.

For me, the advantages are obvious. All markdown code is written in the same way across the project, especially where there where are dozens of markdown files in the project (e.g.: maintaining a whole project wiki in markdown). Moreover, there are many different ways (aka. flavors) of writing markdown files, which can be mixed in a single file. This confuses me even more and I'm asking myself why they don't see the benefits of that.

Here I would like to ask you. What is your opinion about markdown linter? Would you find any advantages using markdown linter in your projects or rather treat it as something completely useless which in the end only frustrate people by keeping the same way of writing?