In reply to Poena.

A few comes to mind, such as not allowed to modify any core WP functions, even when it's at the theme level for style purposes; Not allowed to remove the archive title label such as Category: Your Category Name; not allowed to modify the pagination with my own; WPTitle restrictions; not allowed inline styles (situations where it's required); screenshot restrictions; no default logos, required to use core-bundled scripts rather than including their own....In many cases, we've experienced requirements in reviews that are listed that are not even in the actual development guidelines...almost like the reviewer added them on their own. I guess I should correct myself to mention that most of the issues are during the review process where you get some cowboy/girl type reviews happening. Like Satish mentioned, it's often reviewer attitudes and a feeling of I'm the reviewer and what I say goes. And when they start adding in their own rules and requirements, or they misinterpret a real requirement, it's a bad experience for the theme author.

Not all reviewers are like this, by all means, I've encountered a few really amazing ones, but there are many over the years that come across like they have something to prove or impress someone.

The whole review process is a cringing experience and often made me think, what's the point. I know many authors have walked away and scares new ones who were contemplating theme submissions.

To become a reviewer, I believe it should be like a job application you go through. You need to also be a people person because you are working in an environment that involves many people.