2) I don’t make FAANG money but I’ve consistently earned 2.5x+ median for a person my age in my area (I’m in like a 3rd tier US city, couple million people, several tech headquarters, a couple of which are household names)
3) FAANG interviews are a game. The point of how awful it is and how prep-necessary is to selection-bias the pool so the vast majority of candidates are suitable, to select for only those who want it bad enough (and/or have lots of free time), to make jumping to peer companies difficult to keep wages down (if that last weren’t the case, they’d find a way to stop doing it for people who’d already passed it one or more times—the process is expensive) and finally to build esprit de corps via hazing (hazing is very effective at that). Don’t take it personally.
if you haven't very recently taken a class that uses CLRS as the textbook, then it makes sense you would have to do more memorization and practice with those concepts.
Basically, the things you need to get good at is remembering the runtime complexity of the main data structures, and to be familiar with the core structures that are available in whatever platform you'd be writing code in.
I was working on a Java-heavy team, so the important thing was to remember the various Map types, PriorityQueues, Stacks, arrays, and being familiar on how the references in Java work. The algorithm stuff wasn't too hard once you have a somewhat intuitive understanding of all these structures and when they're useful.
For example, one thing that they seemed to love in interviews was having you implement a least recently used cache, specifically an LRU cache where every operation is constant-time. Easiest way to do that is to build a doubly-linked list and have those point to a wrapper type inside a hashmap, it's not terribly hard but it does require familiarity on which data structures are useful. In this particular case, the rookie mistake it so try doing it with a minheap.