If they are using height data its going to be an approximation and its only accurate to a certain distance usually in the 10's of metes for free public data, regardless, I'll be doing it manually, I don't belive there will be any notable trade off, especially when you factor in if the intention is to produce 3D models, a level of decimation is required at run time to keep them at sane levels of geometry anyway, so you are generally ALWAYS getting less than what you could potentially get for practicality reasons, be that poly count or rendering time.
I use an independent camera with home made mount and FPV, it produces much better results than the X5 as each photo has nearly around double the megapixel count of the X5, more megapixels = more accurate 3D data, assuming same focal length and distance. I compared it next to the X5, its a good 25%, so that is why I go with the less enjoyable solution as the quality is the only thing I really care about.
Don't get me wrong, I miss the all in one capability of the X5, but if you want those extra megapixels, you have to go custom.
I wish there was a sony A7R II solution out there that just worked out of the box.
42 Mp photos.
Full frame sensor.
Video which is good enough.
All stabilized without jello, hassle free workflow.