Nope. A deck is model, data, state and maybe presentation. The game is logic.
A game is not a deck. A game uses a deck. Really basic OOP since we're going there.
Why stop there?
What about layers, filters, transformations, scanner and cloud support. Yes, let's add SOAP, REST, FTP and Kermit support in case need to transfer these images between systems.
Why do we need different classes at all? We could just create a single class that does EVERYTHING.
You're confusing high level ease of use with low level architecture. The difference between the VCL and f.ex. ImageMagic is that one of them has it and the other doesn't. I'm guessing you've never read through the ImageMagick source code since you use it as a reference. I have. It's written in C. That might give you an idea of the inheritance scheme it uses... No?
There's really no point in me trying to explain my point further since our reference frames are obviously worlds apart. Good night and good luck.