The added cache isn't free; the CCD with vcache runs at a significantly lower clock speed. If every task was always put on the most appropriate CCD, the heterogeneous approach is pretty much a direct advantage, as frequency-sensitive workloads get high frequencies and cache-sensitive workloads get lots of cache.
Whether it will ever get good enough at picking CCD remains to be seen though.
Perhaps but I have no idea how any scheduler can possibly figure out if a workload is frequency or cache sensitive. The current strategy seems to be "if game, use cache, else use frequency" and it sorta works OK-ish? Although then there's games that aren't detected right (like Factorio) and it's then a terrible result.
But if you look at single threaded results with it set to "prefer cache" it's not really that much slower. Yes you'd have a flagship with lower single-threaded Cinebench results, but I mean that also happens with pretty much every HEDT platform and nobody bats an eye at that. The results are still a significant step beyond the 5000 series single core results.
Whether it will ever get good enough at picking CCD remains to be seen though.