Do you want to make games or LEARN to make games? Consider this very deeply and come up with a polished answer. Unreal Engine is a nice tool, but it does not always serve it's purpose. I, as a code-oriented developer try to avoid UE4 in any possible way, because it forces the user to think in a very specific way, and that is totally opposing to what I believe game development should be about: (theoretically) unlimited freedom of choice.
In regards to your question: Here's how I see it: Do you want to be able to make any possible game? Then you need a very wide skill set that is not bound to any specific interface or API. If you want to learn 2D graphics then pick up SDL/SFML/OpenGL/(whatever) books and start learning. There is nothing more satisfying than beginning at the very bottom and working your way up to the top: you'll never fear the learning curve, or the entry bar again. Try to explore every little nook and cranny of this infinite field and see what's getting you excited. As a matter of fact, most companies in game-dev avoid UE4 because, while being a very useful multi-tool, it also fixes the way developers can do their work.
On the other hand, UE4 will give an experienced developer a tool set that will increase their productivity A LOT. However, UE4 does come with a very steep learning curve, especially for developers.
As an example, consider that in UE4 you can't use the C++ Standard library in the way you might be accustomed. You need to either create your own algorithms and data structures or use the built-in functionality, such as the TMap or the TArray, which you need to study very closely before you are able to build anything with them. You might say that you can avoid coding completely, by using Blueprints, but you should be aware that Blueprints bring a powerful performance overhead: they are meant to be an interface between designers and programmers, not a programming tool.
TL;DR: UE4 is a next-gen game engine that has a high hardware impact even though you only want to use part of it's functionality(that is, you get the whole minimal package at all times), and has a very steep learning curve especially if you're a programmer. Before doing anything with UE4, I recommend you try to learn with a 2D wrapper for OpenGL or DirectX. Try SDL, or SFML. Or you could go for OpenGL directly(it's very satisfying to climb the initial learning curve and draw your first 3D cube that spins around in the post 3.3 standard).
I hope you'll consider what I mentioned above and won't stop pursuing the elevation of your creativity and experience.