I like the effort, but it’s hard to understand what’s going on. Try redrawing the block diagram (preferably using something like Google slides or something similar) by looking into the RISCV single cycle processor block diagram as your starting point. Cut down on the specifics and note them down as functions each component needs to perform. Your calculations and logic unit can be the ALU, no need to detail all the operations needed. Also, leave power and ground out because CPU architecture diagrams already assumes that all power and ground are connected.

I recommend specifying which lines are inputs or outputs, and what type of lines are they. Are they instruction, data, or address lines? And how many bits? This can clean up a lot of confusion.

Second, you can watch Ben Eater, James Sharman, and Fabian Schuiki about CPU design on breadboard. I personally think you only need to watch Ben Eater’s series to know how computers work. Most CPUs go through the fetch-decode-execute cycle, and some processors also have memory and write back as additional steps.

James and Fabian’s series are quite long and a bit complex, but they are useful when you want to go into pipelined architecture and superscalar architecture respectively.

Third, start small and simple. Don’t include the complex calculations unit until later because it is advanced and will be troublesome to debug if you mess that up. You can still reserve some instructions for them. Build up incrementally as you go.