What you have listed is absolutely correct, as far as it goes. These are a couple of caveats, of course.
First, what you say ignores the fact that
a) If you watch the values in the resource monitor for a while, you can see those figures going up and down as the app draws up or frees RAM. Note, there is a well known problem called RAM leakage which can affect your PC if an App isn’t behaving correctly, where RAM is allocated, and when the app has finished with it, it doesn’t get put back into the RAM “pool”, but becomes unavailable. This is not normal RAM management, but rather a bug that needs squashing.
b) Below the table you refer to, there is a bar graph which shows you graphically just how much RAM is in use at a particular point in time. If you watch it, you will see values changing over time, as RAM is used, and freed up.
My example below is of a fairly boring session on my non-FS PC, but you can see the graphic presentation that I mentioned.
About the only aspect that doesn’t appear to change is the tiny amount that is Hardware reserved. The rest is quite dynamic.
There is a tool called RamMap that will free up RAM if you have a need to do so:
And here is what the resource monitor shows once you have cleaned out all the unnecessary RAM usage.
You’ll notice that so called Hard Faults has jumped after running RamMap, and freeing up so much memory.
Hard Faults aren’t faults at all, but rather an indication of the use of the swapfile, which, by freeing up actual RAM, is where a lot of that data has to go to.