In the end that I think the rigidness of province borders you notice is mainly a function of the map size.
When I shrink down Clio from the original V1 size to the size of HoI3, the borders between provinces simply become more angular, less free flowing, because there simply are not as many pixels in the image to base the borders. Clio for V1 has a size of approx 29500x15000 pixels, the HoI3 map is approx 5200x2700 IIRC, or about 1/9th the size. Borders will simply not be "flowing" to the same degree they would be on a larger base map.
Unfortunately, video cards simply can not handle a map as big as Clio for V1 with the functionalities that the Clausewitz engine expects from the video card for maps and graphics. Going much bigger than HoI3 size basically gives video cards with dedicated 256MB memory seizures, forcing it to borrow from the main system memory, causing massive slowdowns, and even higher dedicated memory video cards struggle with even a marginal increase in size. At this point, it'll be a good while before the dedicated memory on video cards reaches the levels needed to run a map the size of Clio for V1 completely on its own.
But if the price for freeing up system memory that would be used to run the the map and other graphical elements being assigned to the video card memory alone is a bit blockier borders between provinces, in exchange for more memory for the AI to do all its calculations, I think it's a fair exchange, and in the future technology should allow for bigger map projections to be used on computer systems affordable to the mass of computer owners, not just the few that can drop up to several hundred dollars on the newest top-end video cards.
