My only pushback on the lasvalidate output is it would be handy to have JSON output too. Other than that, I think it is a mistake to generate output from tools like lasvalidate or lasinfo in unstructured formats like CSV (or worse is stdout unstructured printf output that can change version-to-version). It just takes some simple manipulation (your language of choice) to reach into these data in programatic ways, and they allow many other things to built atop them without a horrid and fragile data translation step in the middle of data workflows.
If you have 30,000 LAS files to validate, you want a simple script that can shred that XML document into a SQL insert statement that captures what you want to query on. This would allow you to write SQL queries and interrogate for all the different ways LAS files can fall over.
My $0.02,
Howard