I agree that it easily leads to usage issues.

Whenever I scanned through my list of feature requests, I thought about a suitable solution for this one.

One could be to make some switch of sorts "enable marks=true|false" which is evaluated "late". This could be toggled at will, and it could override the current marker to none if it is false (without loosing the current marker if it is reenabled).

Would that appear to be useful? I fear that it causes usability issues at the other end - caused by the very same weakness as "no markers". After all, why should someone say "no markers" in the first place? Only to override the cycle list ... but the "no markers" name does not really indicate that it has anything to do with cycle lists. And neither would "enable markers". Not really satisfactory in my eyes... does it sound better in yours?