Interrupts and polling Are Interrupts really just an abstracted form of polling?

I saw a system-file-watcher library that stated it used polling, as opposed to listening for events. Is the .NET framework SystemFileWatcher class just an abstraction of polling?

In a computer, interrupts are stacked, and the CPU checks the interrupt stack after every cycle, so this is pretty much polling, right? - Albeit more efficient than checking every individual device.
Not really. 

Polling requires CPU cycles to poll a device and respond if needed. Detecting interrupts takes up no extra CPU cycles and is almost always done in parallel with instructions being executed. CPU cycles are only used up in servicing the interrupt. 

Also, with polling, you have a control over how and when you poll devices whereas interrupts are generally out of sync with the program (or at least, you cannot exert too much control over when they arrive).

The mindset behind polling driven and interrupt driven code/architecture is entirely different.