One of my tricks for trying to "find" a track that just won't allow itself to be heard no matter WTF I try is to look for something else (a track, bus or folder) that accidentally got solo'd. Basically go through my project and UNsolo everything.
I know, it's weird, you can hear it playback, so what I'm saying doesn't seem likely, but still, nothing else you've tried is working, right?
Maybe a bus? One hint is that your reverb send is working. It sounds like you're using a send bus to do your reverb, so there might be something over in Bus Land.
I believe this one dates back to the invention of the "solo" button on physical consoles. :-)
I'll second what brundlefly suggested about trying to route the track directly to the output. Put me in the camp who suspects routing or the wrong combination of mute(s) and solo(s) rather than a corrupted project.
Also, I
don't monitor through a separate outboard mixer or via my interface. I use Sends and create Cue Mix buses, which lets me set up and store as many custom cue mixes as I wish without having to touch the main faders.
It requires a bit of sleuthing to find plug-ins that induce latency and therefore should be switched out while tracking, but Cakewalk (and yes, once you finish this session look into installing Cakewalk by BandLab) has a button that will bypass all of the effects in a project.