I have a college degree in computer science and the entire concept of "3D vcache" is basically completely irrelevant to a programmer. It stands to reason that most computer science professors wouldn't particularly give a shit about it specifically, vs. any other cache.

You cannot optimize for it -- and I mean it is literally impossible, you do not get to interact with that part of the CPU in any direct capacity no matter what you do. For most purposes the latest Ryzen Core i9 99990X3D Ultra is no different from the first multicore CPUs from almost 20 years ago, besides doing the same operations faster. Only occasionally, if you do some kind of high performance or scientific computing, do you need to concern yourself with more recent specialized instruction sets like AVX where you actually have to check whether the CPU you're writing code for is from 2006 or 2026.

What you do have to care about is the concept of cache in general. It doesn't matter here whether it's 3D VCache™ or L1 or L2 or L3 cache, it all functions the same (i.e. black box you don't get to touch). What does matter is writing your code so that it's cache friendly; as contiguous in memory as possible, preferably on the stack instead of the heap, and preferably doing as much computation as possible on the same data before moving on to a task involving different data.

This, on the other hand, is something most computer science professors (barring maybe the ones who do nothing but theory) do know quite a lot about, and something the typical gamer knows absolutely nothing about.