mika
yes, that would be possible (maybe faster than converting again, at least for large clouds).. but then again, iterating hundreds of files wouldnt be too fast either.. (at least if...
if you send me an email, i can attach the v2 translation shader version for testing. for v3 tiles: Is it enough to move it during Start() to match transform...
made initial tests for this issue, works if manually loop & offset loaded points, but that would be slow.. so it needs custom shader that offsets points too. this should...
ok, it works for the basic v3 viewer, not packed version yet.. offset is applied on start and then possibly can be edited later from script too. 
could add queue for clicks, then can click many times (if want to allow that), while multiple threads are calculating results.
For mobile (and android+quest 1/2) only pointcloud2mesh is supported, https://github.com/unitycoder/UnityPointCloudViewer/wiki/PointCloud2Mesh (it creates regular unity meshes, with from point cloud, with point rendering and custom shader). But, its quite limited on...
Recently tested Quest 3 standalone builds, 5mil. mesh points (from that mobile demo scene): 30fps 10mil. :
seems to only happen if las/laz tile has points outside its own tile bounds. for example laser scanned house: - scan 1 will have (stray) points in scan 2 area...
are you using BiRP/URP/HDRP?
ok ill test / check