* ...the blurring of the distinction between output and code.
* ...the distinction between name and thing-being-named. (The different "x"'s in my example, within different levels of nested quotes.)
* ...leaky context (local variables defined inside the eval scope ending up outside the eval scope, and vice versa).
Harder quines tend to hide all that behind layers of tedious encoding.
If you're really interested in hard quines, you might be interested in trying to dig up some fully-detailed proofs of Godel's incompleteness theorems. It's the same story there: elegant and beautiful ideas, drowned under mountains of tedious encoding.
As a compromise, one could imagine a quine which works by writing programs to disk and then reading those programs (as opposed to reading itself). This would be kind of silly, since the same data could be written to/read from RAM much easier.
They are a matter of taste.
Eval. Reading the source.
These are quines by some narrow technical definitions which skates along the surface, but misses all of the beauty.
Maybe the aren’t cheating. But they aren’t special. They might not be disqualified, but they score — at best — 2/10.