If a question happens to not describe the problem that it is having and, for example, just dumps a bunch of code with a "plz fix" then it's a bad question that should be downvoted and closed regardless of whether the problem is a syntax error or some other type of problem entirely.
If a question doesn't demonstrate sufficient effort, hasn't indicated the research done by the author and what they have attempted to do to solve the problem then that is also a sign of a poor question, to be downvoted and possibly closed as well. Again, this is regardless of whether or not the question happens to be about a syntax error or not.
We already have tools available to handle the types of syntax error questions that are of low quality. There is nothing special about the fact that they are asking for something relating to a syntax error. They can be downvoted/closed based on what's actually wrong with them, rather than simply because they are related to a syntax error.
If a question describes the specific problem, demonstrates a minimal understanding of the problem, has demonstrated effort and reasonable attempts at researching the problem, posts a clear and understandable question, etc. and that question happens to be about a syntax error, then it can very well be a great question that is entirely on topic on SO and most certainly doesn't necessarily belong on another site just because it is a compile time, and not runtime, error.