Short answer: Probably
Long answer: Don't bank on it.
See this question for a more complete explanation, but while content type checking works today, you can get pretty close by posting valid JSON as text/plain which may be incorrectly parsed by some backends.
Additionally, if enctype='application/json'
ever becomes valid HTML, your whole system is pooched.
While it's a great first step, if you really want to protect against CSRF attacks, implement a proper CSRF token system.