u/HexadecimalHero: going into games could be great for you in many ways:
* You can do it on your own
* There aren't as many accessible games for consoles or mobile devices as there should be
* You don't have to build, deliver, or support hardware
* You don't need a decade or more experience in engineering to get serious about it.
As someone who has worked in image processing for decades, including applications of optical character recognition (OCR), I'll say this is MUCH harder than it will seem at first. Try some OCR apps for your phone and see how they perform under changes of lighting, at different camera angles, reading signs instead of text in books, with the text partially covered, etc. Focus especially on the failures, not the successes--how much/little does it take for the algorithm to yield the wrong text? Or to read nothing at all?
For engineering--even for tinkering and inventing--you need to write specs for yourself. Under what circumstances will your thing work? How well? What is an example of it not working well?
For OCR: what is the typical read rate achieved under the circumstances you mention? How do you know? And is that read rate good enough? How do you know?
"... after having read and watched numerous videos and articles ..."
You will need to work your way through at least one textbook on image processing. The mishmash of opinions, presentations, lessons, pointers, etc., that one finds online still doesn't compare well to working methodically through a good book, likely an introductory textbook for engineering undergraduates.
Digital Image Processing by Gonzalez and Woods is a good textbook.
$1 Machine learning is certainly NOT enough to solve this problem. If you know Python you can get a lot done, but you'll want to learn C++, the language that has dominated image processing for decades.
"Subsequently, I noticed the problem of reading but mainly reading where the person does not know they need to read, which is described online as impossible."
It's not quite clear what you mean here, but take opinions you find online--including mine--with a grain of salt. Saying X is impossible without providing good specs for **exactly** what X is, is basically saying nothing. It's easy to grab some sample code, run a few quick tests under nice conditions, and then claim to "know" about the application for which the code was intended, but I can tell you from interviewing quite a few engineers that this approach doesn't hold water.
All that said, mixing image processing + games could be wonderful. You could also start with a much simpler image processing problem: track something in the game player's hand, and use that as a means of interacting with the game. Even a "simple" problem like tracking an object of known color and size gets tricky.
Good luck!