Update on performance in the expectation that this data may become publicly available in the future.
Kevin you were right by suggesting sticking with a single LOD. By selecting only one, highest, LOD (sliders both to the right), It cuts the render time down significantly, to the point where it becomes a usable model for interaction in Unreal 5. Neither Unreal nor ion cause the model to visibly snap to different LODs on approach, but the area size I care about is small enough that it can perform fine. Did not notice performance or visual difference between 3D Model Asset and 3d Tile Asset btw. When I circle back to the data capture side of things, I’ll take the approved API approach and hopefully come up with a more longterm legitimate solution. Thanks again to Kevin for assistance.