Your Unit:
My comments had allot more in suggestions other then unit speed. I did tested in Flicster & Civ3FLCEdit. I have found that units that look good in those two typically look good in game. There are the occasional exceptions, but it is good for a rule of thumb.
The biggest problem with the victory is the guy's motion has not relationship to the action the weapon takes. The Baton-twirl might work better if he bent his arm and wrist some. Suggestion: if you want to include such action, act them out a little ant take note of your joints and positions.
I don't dislike your attempt at a unique victory, etc... I do this myself. I think such exercises make great learning tools. I use them that way myself. I learn more from my failures then my successes. But, you have to be prepared to not use stuff when it doesn't quite work. I think the baton-twirl done allot lower (torso height) would make a for a very interesting fidget.
Civ4
Tell me I'm wrong, but offer no facts to support your position. The "is not, is too" method of debate is not my preferred method. So, we shall see on the unit creation; I hope you are right, but I followed the mod-threads fairly closely and there is nothing there to show we can make units the same way or using the same tools. In fact the in game units are quite nasty low-poly looking.
The word from the experts was 3ds max would be required. Later it was said they "might" come up with a way to import Civ3 stuff. But this is a unsubstantiated rumor and was never attributed. In other words someone seems to have made something in a rush of wishful thinking. The look of the units in game supports the original info. Low poly meshes made in 3ds Max with medium to high detailed textures. The result is mostly inferior to Civ3 units. Where the best of them are high-detail mesh & high detail textures.
Poser does not produce proper meshes. It can be used to make limited OBJ meshes, but it is a animator more then it is a modeler. This considerable limitations, this OBJ can be converted to a 3ds but you will lose the textures. POVRay is both a modeler and an animator, but it does not produce a 3ds compatible mesh at all. Bryce is a crummy modeler, but brilliant animator and is especially good at hard surface units. It can use a 3ds mesh, but it can not produce one. The list goes on and on.
Now consider the % of the human type models made with Poser, most of them. Consider the hard surface models made in Bryce, a VERY large percentage when you consider that Wyrmshadow alone has done 4-500 units. Add in Aaglo and Orthanc, both prolific POVRay users. UtahJazz = Poser, and others using other programs with either very limited or no 3d max compatibility. This completely ignores the fact (for simplicity sake) that almost none of us own or are willing to buy a 2-3000.00 software package to make Civ units.
I just got a copy of Civ4 Special Edition for 1/2 price from a co-worker that bought it and hated it. So, while I remain firmly in the Civ3 camp, I will investigate it more fully some time this weekend (time allowing).
It will be interesting to see what the SDK includes.