Unfortunately, it will not be possible to integrate ourselves.
The sensor is plugged into the VEXos CPU, meaning that with the architecture of the V5, the bridge between the user CPU and the VEXos CPU only updates at 10ms. This means the user only has access to 10ms sensor sample rate, making it nearly impossible to integrate or even remotely beat VEX’s integration which can run at 1ms on the VEXos CPU.
This means that we are fully dependent on whatever integration VEX chooses to do.
The reason it was possible to do custom integration on the Cortex system was because the user had access to a much higher sample rate.
Furthermore, measuring distance is also likely unfeasible. This involves double integration (acceleration → velocity → distance), which requires some really expensive sensors to properly pull off. Not only are we dependent on VEX to try and do it for us (which will likely be pretty hard for them), it would be magnitudes worse for us to do it on the user CPU.
These limitations of the V5 architecture make the accelerometer have quite a limited use. You might be able to use it to detect collisions or something, but good luck trying to do anything sophisticated.
Edit:
Here is a diagram from the V5 architecture page that shows how distant the user code is from the sensors.
