You might not notice the difference, but that guy at Apple who's only getting 5% of his usual haul of bitcoins this month sure will!
Flash is running an event engine like JS under there. Your comment made it occur to me that they might busywait, rather than having a proper scheduler. This seems insanely lazy.
It's not a busywait, they use the extra CPU to render additional animation frames. But half the time the difference is not visible anyway.
The bizarre part, when it comes to Flash, is that I've yet to see an actual difference in the application behavior when I throttle down it's CPU usage. I would think that if it normally maxes out 7 of my 8 logical cores, being limited to 40% of one core would make introduce slowness. But I guess that's just an indication of how poorly written the OS X flash client it.