Yes, I can confirm too. Strange.
Thanks for replies, at least I know its not just my camera!
a1ex already gave you the answer to what is going on, it's seems maybe the answer passed over your heads:
the palette registers are write-only, so if you are able to get the palette values, be my guest 
Translation: we don't know what the
color values in the bitmap vram (overlay screen buffer) are supposed to mean.
Canon firmware sets up the
color palette for it's graphics, and we can't read the values directly from the display registers that control the palette, they are write-only (figuring out the current color palette would require reverse engineering the Canon code that setups the color palette and patching it in a way that allows us to keep track of the palette; a1ex says that if you are able to do that then "be my guest", implying that it would be a non-trivial and time consuming task; I suppose all the recent
qemu advancements booting the Canon GUI would be a great help to this end).
All of the other screen captures I tried turned out fine.
Screenshots of ML stuff looks correct b/c for our graphics, we know what the palette is.
Screenshots of Canon graphics on other cameras look incorrect too, but not quite as crazy.