You have described about 1/4 or 1/3 of the work involved in the addition of a new nation. (Assuming the OOB is solid, and fits in with the existing OOB "standards" etc). You have only done the data, there is programming to be done. This is a game, so the data is supporting but not primary, unlike a database aplication to track widgets or whatever.
One then has to do a pick list (which may need to vary with opponent), for 1950-2020, which is decidedly non-trivial.
One then has to ascertain the national batlocs, may require new ones etc, again you then need to decide what happens when particular dates, opponents etc come into play.
Then the internal data structures for air control, counter battery, leader quality, troop quality etc need doing.
Then it all has to be hooked up to UI code for battle generator, scenario editor etc.
Oh - and I am assuming there are
no new SHP files for the absolutely vital "Whoflungdung Mk32" rotary muck-spreader and suchlike that the new nation needs for "fidelity"
. That might need new SHP files (and there is only limited space, if any, for new flags in the existing UI SHP files).
Then, there is the slight problem that the UI flag space is 100% used, and we no intention to rewrite the battle generator (and several other UI pages) to support multiple pages.
Therefore, unless there is a really, truly, compelling reason to include any new nation - it will not be happening.
Cheers
Andy