EDIT. Gatdam JC posted before me.

I dedicated my post explaining how the CPU/RAM work together, but things work more or less the same with GPU/VRAM, and other important factors like PCI-E frequency et cetera.
I'm gonna reply in parts to get this all straight.
If you want more FPS you go and buy more RAM, right? 8-)
Like I told you like 3 times, if your RAM is sufficient, then no you don't buy RAM to improve performance. If however your case is something like this:
All I know is that Oblivion runs shitloads faster now that I have 2gb of RAM rather than 512mb. 'Nuff said.
Then yes, you do go and buy more RAM to get better FPS. Just because CPU and GPU are the biggest factors in deciding game's FPS, doesn't mean you can just throw other factors out of the window.
In most cases you get more FPS by upgrading CPU and/or GPU while RAM (and other storage) would affect the loading times.
Absolutely, in most cases you get more FPS by upgrading CPU and GPU. But it isn't in all cases. The flaw in your argument is that this whole time your argument has been based on a fact that you have enough RAM and it's fast enough for that CPU upgrade, but you don't really understand how the big picture works. You just think everything works independent of each other. If your RAM can't keep up with your CPU when it's necessary, that precious CPU upgrade of yours can end up being
useless. Let me tell you why (again):
1. Let's say you have 512 megs of RAM. Now let's say that an application requires 2 gigs (or 1, anything more than what you have available really, the bigger the difference, the bigger the following effect will be). This is what will happen. When your operating system notices that your memory doesn't have enough space to store all the data that the application requires, it'll start using your HDD as memory to compensate for that. This is what we call "virtual memory". The process of the system transferring data from or to virtual memory, is called swapping (or paging). Swapping is slower than reading the data from the RAM's storage.
Much slower. What this means to you is that your brand new CPU will sit there and do nothing (i.e. idle) while it waits for your system to read or write the virtual memory. If you notice that your system does excessive swapping,
your first priority is to get more RAM. Not upgrade your CPU or GPU.
2. Another big factor is the RAM frequency. I'm gonna make this example pretty exaggerated so you'll get it. Don't pay attention to whether a mother board exists that these parts would be compatible with in the first place; It's not the point here. Let's say you got 2 gigs of DDR2-400 (PC2-3200), now let's say that you just upgraded your CPU from some old single core CPU to a Core 2 Duo E8400. You will notice a performance improvement, but you're still
severely limited by your shitty RAM. Let me tell you why! With DDR2-400, your memory's bus speed (i.e. DRAM frequency) is 200 MHz. E8400 FSB (non-rated) is 333 MHz. When you want your CPU to performance to its specs, you want to make sure that your FSRAM frequency is 1:1 or something near (note! this is about DDR2, DDR3 works differently). In this case the situation is the exact opponent. Your DRAM frequency is a lot slower than your processor's FSB. What this means that applications that require high memory bandwidth will have a
noticeable performance hit, because your memory bandwidth is so much behind what your system could handle, thus once again making your system idle unnecessarily. By upgrading this RAM to something like DDR2-667 or better, you should notice a noticeable FPS increase in games and applications that require high memory bandwidth. Don't belittle the memory's influence on your overall game performance. Just because you happen to have fast enough memory and enough of it you make these groundless statements without really understanding how the system works.
In my view, when the game begins loading the game is "paused" for that period, and thus not really affect your real FPS. A good example is a modern MMORPG where you have many zones, and when you walk over to the next one the game is "stuck" briefly in loading. Your FPS before this loading was 60 and is 60 after the loading, means your FPS still is 60. The game just stopped to empty some storage to get new stuff in.
We're not even talking about loading time FPS! Why did you even mention this? This is so obviously irrelevant to the debate at hand that I don't even bother commenting it any more than this.
In my view the total performance of a game is smoothness which FPS is part of. FPS being the part done by processors of the computer.
Well as you can see from the poll right here, your view is quite off, and FPS is not used as measurement for processing power. That's what we got flops and mips and et cetera for. Those are
exclusively for that purpose. FPS means how many frames
you see on your monitor per second. The term is so self-obvious that it's beyond my understanding how you can even get it this wrong. Also I remember you mentioning on IRC that you've noticed stuttering etc. without FPS drop. There are various possible causes for this. The first thing is that FPS as a measurement unit is pretty bad as it is. It's not very accurate, because it doesn't account to fluctuations that occur during small time frame, time frame that human eye can see though. For example when stuttering happens, it can happen excessively for like 1/8 sec (which would be very noticeable by human eye), but have a very small impact on the FPS, because 1/8 isn't much in second's time frame. There are also times when things happen that make stuttering appear, that the game's FPS counter can't simply detect. For example, a bad cable or bad scaling on your monitor are possible causes for this. There's no way for software to account for these kinds of things in the code that keeps track of the FPS.
It's RAM's (and other storages) job to keep the loading and stuttering at minimum.
Wrong. First of all, stuttering can be caused by a lot of things. Yes, too little or slow RAM is one of them. Other reasons include, but are not limited to: overheating, too low voltage, monitor / GPU sucking at scaling if not running native resolution. You can't just say that "hey this is the memory's job" and completely overrule all other factors. Computers aren't that simple. And as I previously stated, FPS isn't very accurate unit of measurement. Just because it's hard (or even impossible) to see the change in the FPS for the reason I explained previously, it doesn't mean the cause is completely irrelevant to the factors that also relate to the FPS, as your logic seems to be.
Also you said on IRC that if you wanted to fasten loading times, you'd get more RAM. It's not that simple, everything comes into play, even for things like that. Buying more or faster RAM doesn't equal faster loading times. Even if your DRAM bus was very fast, it doesn't do much good if your CPU bus doesn't keep up (when loading, the data isn't just magically transferred from HDD to RAM, a CPU plays an important part too; for example it does unpacking).
Of course processors and storages affect each other so they indirectly affect each other.
No, they affect each other directly. There's nothing indirect about how they interact.