Hi Paola,
The ADC module can be triggered every 2us provided the ADC conversion takes less than 2us.
And you could route the LPTMR0 trigger via TRGMUX to a TRGMUX_OUTn pin and scope the signal to verify it.
Similarly, you can route the ADC_COCO trigger to TRGMUX_OUTn pin.
Then, on the pins, you could see when the ADC was triggered and when a new result was available in the result register.

However, you want to get a new ADC result every 2us and send it out via UART.
I don't think there is enough time to do that.
You may try simply storing the results to SRAM and then read the results using debugger.
Also, if you want to get ADC results <2.5V only, you can use the ADC automatic compare function, Section 44.5.5, RM rev.12.1.
The SDK ADC PAL driver does not support this function but the S32K1xx ADC SDK driver does.
You may refer to the adc_hwtrigger_s32k144 SDK example.
Anyway, as I mentioned in my previous post, the SDK drivers cause significant CPU overhead.
In this case, it would be probably better to use non-SDK code.
Something like this example: S32K144_Project_PDB that can be found in the S32 Design studio as well.
It uses PDB to trigger an ADC conversion periodically and the result is available in the ADC interrupt function.
On top of that, you could use DMA to transfer a certain number of ADC results to SRAM without using ADC interrupts and the CPU.
Regards,
Daniel