this is very interesting.  I've considered writing something a bit like this myself.

Have you considered automated varying memory clock too?  (effectively making this three dimensional -- a stack of graphs like you made)  I ask because I've read hints that suggest that there exist lower 'sweet spots' of gpu/mem clock that exert similar, or slightly lower hash rate at a much lower power draw.

for me, I'm more interested in lowering power draw and gaining per watt efficiency.  with the stack of graphs you could draw a curve of optimal hash rates vs gpu/mem clock.  I would expect that the latter is predictable (thus not needing to be strictly measured) and might help produce a final graph of optimal settings vs clock level/power draw to let the user decide if jacking up to max hash is worth it to them.

linux version would be nice too :-)