The laws Google asked for changes were not limited to the mapping laws but any law to require domestic data centers, which might trigger the domestic tax issue at any moment. Your explanation that Borg couldn't handle domestic clusters doesn't clearly explain that Google eventually established SK data centers and started supporting vector maps anyway---and given that South Korea is not the only country with such requests (e.g. EU), not being able to cope with such laws is just a Google's fault.
Google data centers != Google cloud data centers
The two are logistically very different and consequently that means the types of workloads they host are also different. The latter is really for GCP usage only (both customers and Google-internal cloud infra necessary to host GCP). Compare https://www.google.com/about/datacenters/locations/ with https://cloud.google.com/about/locations.
1. SK vector maps were generated using domestic servers (but no Borg) as SK govt demanded.
2. Google "secretly" exported SK maps and generated vector maps using Borg anyway.
And both scenarios are problematic. The former would mean that the GP's claim that vector map generation requires Borg is not true or at least exaggerated (this scenario was what I had in mind when reading my sources, hence no verification). The latter would mean that... well, Google is in direct violation of SK law and not even trying to hide that.
Tax reasons might have arisen since, but maybe we're talking about different laws? I don't know. Do you?
The fact that there's no mention of Seoul at "Discover our data center locations" https://www.google.com/about/datacenters/locations/ tells me that its GCP region is most likely rented space in someone else's buildings and there are no full-blown Borg clusters with their usual tenants. Choosing where to build was always a complex process. There have been cases where announcements were made and land was bought, but nothing ever got built.
My explanation that.. "Borg couldn't handle domestic clusters"? What does that even mean? You could probably bring up a toy single-master Borg cell on a workstation with the right 283 command line flags and a toy Chubby cluster, but that still won't give you any map tiles.
Back in the days before incremental map updates, the whole globe's data came from a pipeline of pipelines and mapreduces, stitched together by a number of teams (the project's codename started with O). It was tracked with advanced technology (Google sheets) by PMs that had a taste for suffering. The latency was measured in weeks and months. If you missed the build, your data or code changes would take who knows how long to go live. I think that sometimes builds might have been abandoned altogether. These were the days when mobile Maps, if they existed at all, lagged desktop tiles by weeks or months (there wasn't one set only...). Same with navigation. The amount of data has only increased since, but there's obviously a much more advanced process at work nowadays. I don't know what they changed or how.
Anyway, back then, to build the SK tiles with the same tools you would have needed Borg, yes, but also Bigtable, GFS and a wide assortment of ancillary services. How are they doing it now? Maybe they finally got a license. Maybe they got a sufficiently limited subset of the full feed. Maybe they did a major rewrite of the code, pipelines and even binaries to make it feasible for that chunk of the planet to be handled by a bunch of bare Linux machines on GCP or AWS in South Korea. You might be able to deduce something by comparing updates there vs the rest of the world, but that takes time and dedication.