Leave the system stuff to people that actually know what they're talking about.
Something is going to limit your speed. It might be the processor, or it might be the RAM, or the disk, or the bus, or even the GPU. It might be that your software is using data structures that don't cache well on modern multicore systems, and you're getting cache misses like crazy. It might be that you're running too much stuff at once and your software is starving for processor time or I/O access.
Your bottleneck will be different depending on what exactly your system is doing at the moment.
For CPU rendering, your CPU (or, more likely, your memory bus) will be your bottleneck. If you're using textures that are too large to all fit into RAM, then your disk will be your bottleneck (which is my lots of RAM is important - the disk is a few orders of magnitude slower than your RAM). For GPU rendering, the CPU doesn't matter much at all; it's your bus and disk that slow you down when you're loading textures (which is why more VRAM is important).
For modeling, texturing, or any other non-rendering work, it's more complicated because your CPU has to calculate any changes and push them to the GPU.
And all this stuff varies from program to program. Blender won't act the same as Modo.
TL;DR it's a lot more complicated than people seem to believe.>>526296
Any CPU will be the bottleneck for some operations. That processor and architecture is modern and fast enough that you're unlikely to get much better performance from something newer. If you're having problems, it's more likely you need more RAM or need to stop trying to mine bitcoins while you render.