Wait a minute, before you spend more money, go ahead and demo Reaper, which I like very much, but I don't think you are ready to make that decision yet. You should tell us a bit more about your comfort level with multitrack software and recording in general before a meaningful recommendation can be offered. I'm going to use descriptive language rather than specific technology jargon.
If you are recording audio, the question becomes what will you do with it? Cubase AFAIK (and Reaper) are "Digital Audio Workstation" tools to integrate audio recordings and MIDI (or just one), allowing you to use loops and projects with global settings which allows you to automate the creation IF you use those feature elements. If not, you'll just get frustrated.
Start off imagining the software as a digital version of a tape recorder. Now that you have a recording in there, the question is what will you do with it in terms of your final product, and how will you get from a to z? Your techniques and skills will drive specific workflow decisions.
Creating loops (creating rules for each measure for example) allows rules based creation you might say. In other words, in your tape recorder, the thing just plays along the timeline. If you create a global project file with MIDI rules for timing, you can create a master template that will allow using chopped up sections of your recordings, for example you can take your riffs and have them repeating according to the rules of the project file. This also helps set up your drums, and I suppose you could say the drums are the most compelling reason to use MIDI if you have no live drum tracks. Even if you do record live drums, there are still benefits to looping them too. If you have no live drummer and you wish to use drum patterns, I would say that at some point sooner rather than later you should go ahead and start learning about MIDI.
If that is the point you get to, I would then say yes, check out Reaper because of its documentation and user community is probably going to be better for a neophyte to learn, but you need lots of patience until you get it. I'm about 3 months in to this process myself, and I have been a musician all my life, and have computer experience since early 1990s (started recording on Windows in 2004). I understand MIDI in principle, but I am not clear on how any of these different choices work, because the tools I want are only available on Cakewalk Sonar X1 Studio (I have an OEM version that came with hardware and I bought Guitar Tracks Pro)...but I might be able to figure out how to accomplish what I need to if, IF I learn more about the tools I have.
I'm happy to keep in touch with things I find along the way, and explaining things to others helps me learn better as well, so hit me up any time. In fact I'll even share my notes with you as that gives me a reason to focus more on clarity. What I normally do when I need to buy something is create my own research reports and summaries. I have lots of notes that might apply to the things you need. The first thing you need to learn is how MIDI changes your workflow options. Think of how a computer allows random access, and you might even download a copy of Sony Vegas video editing software, because the workflow with video editing software is very much built like the basic DAWs, and some DAWs even add video options, so we have some conversion here. But usig it with video helps you see visually how the data can be arranged, and it will perhaps be clearer when you then start to figure out your workflow in audio.
IMO, the biggest confusion for a new user to the DAW world is that MIDI and looping have made workflow so flexible that people gravitate towards their own preferences, but this makes it harder to pass on training to others. You kind of have to take it slow at first until you understand what all of your options are before you can decide how you want to proceed, and because there are so many options, you can't even think of the right questions to ask and the experienced people can't really start with zero and say "ok, follow this list" because there really is no ideal approach.
What I would like to see is maybe a thread discussing these things, to give people a reason to contemplate and justify their approaches, and we might get some good lessons from that, but I have never seen such a discussion and I find MIDI a lot harder than it was teaching myself video production on nonlinear video editing machines. Let me say that again, learning how to build music in MIDI is harder than video editing.
As long as I'm on this topic, I'll add one more thing. I think culturally we do not encourage peopel to ask questions. I think that most MIDI masters who learned on their own can't possibly remember how they built their skills in some way that they could explain. Some additional reasons are that many artists have no problem in letting the process influence their final results. This means that they will start wherever they have early success. You figure out drum patterns, experiment for a while, figure out how to add loops of your guitar chords and build like this, this is a good way to learn, but people some times prefer to build their vision (audio vision), and can be impeded by their inability to accomplish necessary ingredients. So just in new users you have this immediate dichotomy, how do you want to learn? Do you want to allow experimentation to shape your end result, or do you have a specific composition in mind that requires you to figure out specific workflow tasks?
If you remember nothing else, remember Hans Christian Andersen, the Emperor's New Clothes. Will you let the naked king walk by, or will you raise your hand and ask the embarrassing questions? Don't let the naked emperors deceive you. It's not that easy to learn, and we all have different approaches because of all these variables, so you have to decide how important those factor are. Do you mind just farting around just to learn what things do? Then try to build anything, any sound, tweak it just to learn. If you need lots of structure, you should probably instead get Cakewalk or something similar because you can buy lots of training material to learn in linear fashion before you know what your options are in terms of workflow. Workflow used to be linear because that was all that was possible. Now the possibilities are so wide in choices that it makes it very difficult for the beginners.