So, you seem to be laboring under some drastic misunderstandings.

Let me try to lay out an example that may make things clearer.

I have a CPU.

A CPU consists of a collection of general registers (data is generally read from and into here), a special set of registers containing metainformation about the state of the CPU, an arithmetic processing unit, and a clock circuit. This is a dirt simple CPU.

Now. If you're using a Von Neumann based architecture, your CPU doesn't distinguish data from instructions. (Modern ones do, but ignore that for now.)

An "instruction" consists of an op-code (basically a number), plus addresses indicating where input data is being read from, and where it's being written to.

So a set of commands for this CPU might look like

load $1 1
load $2 1
Add $1 $2 $3

Assuming we're "wired" into some input pin the CPU knows to listen to, we're running a rudimentary set of computations. We're sending in some number that the CPU recognizes as the beginning of a "load" command, it looks at the 8 bits or so following, and loads 00000001 into register $1. Done for that cycle.

Next cycle, same deal, but in register $2.

Next cycle, we send the contents of $1 and $2 to the adder, which outputs the result into $3.

Easy right?

Now. Let's do some REAL computation. Let's say I have a ridiculous amount of data to crunch.

I have 30 8 bit registers for general use, and my 5 or 6 special registers, and my input pin.

But I have 300000000000000 8 bit numbers that I want to add!

I can make this work with just the CPU logic. I can do a bunch of serial computations, then record the results by hand, and re-input that result as an input to the next computation over and over again, But dear God, that's boring!

Wouldn't it be great if somehow, I could stage all of my information ahead of time, and somehow have the processor look up that information to do it's calculating, with out me having to remember everything for it?

The answer to that conundrum is Random Access Memory. It's a separation of concerns if you will.

CPU's do computation. That's what they are for. Doing the stuff that might cause a state change. We don't want values sticking around in the processor that aren't changing if we can help it. Once something is done we want it out of the processor so we can accommodate the next state changes.

In CS, we tend to have two main axes on which we measure the footprint of computation: CPU time, and space (memory footprint).

If I have high space constraints, I can set up the CPU to handle all the state, but for every new computation, I have to reset everything back to basics, and still keep track of all my information. This quickly turns a simple one cycle operation into many cycles worth of operation and bookkeeping about where everything is.

Or, If I have memory to write to, I can do my computation, write it out to somewhere that's memory managed, and let the magic Memory Management Unit feed me new data and instructions while also cleaning up results, and holding onto them elsewhere on the motherboard so I can use my full CPU die to do computations more quickly.

Look at it like having a helper to get books for you at a library while you're sitting at home reading books and doing math problems.

The library is RAM, you are the CPU, and your home is the CPU cache. Without your helper fetching books for you, you have to stop all the time, and take the books you're done with back, check out new ones, go home, and only then start doing math again. (You're not independently wealthy, or psychic, so absurdly big house, or magical access to all of the books by telekinesis is not allowed, sorry!)

With your helper, you're doing math (yay!), and he/she's swapping out books to/from the library to keep you running smoothly.

Try not to get caught up thinking about wires. Circuits have about as much to do with Computer Science as a scalpel does to Surgery. They're a tool. Nothing more. The important thing is to understand how all the pieces work together to create a functional whole.

If you're still confused about why RAM is a thing, let me introduce you to

https://en.m.wikipedia.org/wiki/ENIAC

A computer that, quite literally, was absolutely dependent on the people around it to play the role of "memory" since each computation required rewiring the damn thing.

Ain't nobody got the patience for that anymore!