There's a handful of projects where the size of the solar field is large enough to make it economic to step up from 400V or 800V bus. I've seen many 1000V buses, a few 1200V and 1500V buses. Honestly it's exactly the same circuits, just with higher voltage ratings; all your switching elements are still giant hockey pucks, you're still doing a three phase hex bridge, etc. The half-assed flyback is sometimes replaced with something a little less braindead.
On top of that they have to comply with a whole host of safety regulations, so even if the theoretical block diagram is as simple as you've outlined it the actual implementation is likely going to be a lot more complex and interesting.
Any pointers to where I can dig around without opening one up myself would be greatly appreciated, most of the youtube stuff is for very cheap or small gear.
Most of the inverter designs offload all the complexity to the software controller in an attempt to keep the power component choice and placement simple. The cool control stuff is mostly available in published IEEE papers, particularly from 2015-2020. It's not open-access, but it's definitely easier to get ahold of IEEE papers than a PV inverter. Once you know what you need to implement, the rest is just software engineering.
The commoditization of computing power, and the continuous decades of improvement in digital hardware performance per watt, has reduced numerous classes of analog problems to an exercise in fast enough bit-twiddling. I think in motor drives the big jump to simple hardware and beefy controller was directly downstream of the creation of usable 32-bit motor controller DSPs, along with software toolchains that made it possible to compile optimized C and C++ libraries for these architectures. Up to early 00's there just wasn't enough real-time computing power available for most of the market to take advantage of it, and what little did exist wasn't directly targeted at motor drives. But it is worth pointing out that the S-curve of digital adoption probably got started as far back as the mid-90s; the only people who could really take advantage of it back then were at the cutting edge with very expensive low-volume projects. I'm sure it felt like an overnight event, but it took a decade for motor drive DSPs and software toolchains to get good enough that most people felt compelled to switch.
ETA: oh gosh I forgot FPGAs happened then too, that probably had a lot more to do with it... Ah well, fun trip down memory lane :)
It's been very interesting watching as the compute gets cheap enough that we can start embedding it into the analog chips. The telecom chips all have DSPs in the ADCs and DACs and digital PLLs in the line cards, the battery management ICs all have microcontrollers for charge management and safety, you can buy radar ASICs for automotive proximity detection, there's gate drivers for SiC FETs in automotive traction inverters that incorporate redundant microcontrollers to do monitoring and fault detection/recovery for ASIL D compliance. So I'd add: the same way that software drives the marginal cost of complex math to near-zero, advances in digital circuitry and ease of incorporation into other analog designs drives the marginal cost of complex application requirements down. It's not quite as stark as software, but it's amazing how much quicker a single complex chip design becomes when you can digitize a subclass of the problems and solve them in real-time at virtually no cost on analog ASICs with built-in CPUs and DSPs. Analog hardware advances are extremely challenging by comparison, and can take years of R&D across a wide array of reliability and performance assessments before they become realized in designs.