A few ideas to help managing the poly count, should it become an issue sometime in the future:
1/ use of the world detail. In AC, this is mainly used for 3d grass, but it can be used for other objects as well. For example, you could place every 5th lamppost on a different KSLAYER. So on Level 1, you only see 1/5th of the objects.
HERE is how to set it up.
2/use of "trees" functionalities. It works the same, based on name grouping. And it does two things: optimize lighting and optimize draw calls.
HERE is some info. I'll add further reply there of a study that
@LilSKi did, on how to make them look best. This is especially useful in case you decide to go for Y/X type (..which I hope you don't

).
3/use of layouts. This allows you basically to split a track in multiple kn5 files, and then just play with them via a simple ini file. Easy, efficient, clean.
HERE is the info.
4/ FPS increase tips,
HERE and
HERE
5/use of LODs. Which basically means you can swap high-poly objects with low-poly versions, once they are far enough and difference is not visible anymore.