4.10 - Mavlink crashes RX firmware when there is a lot of telemetry data

## Current Behavior

With Ardupilot and many active sensors it happened to me that the rx stopped working, losing the link with the radio control and with the flight control.
Most likely frozen firmware as it wasn't responding to anything.

## Steps to Reproduce

I think it's a difficult situation to reproduce because you need hardware with many sensors.
In my case:

- Cube Orange Plus (flight control, three IMU)
- 2 x HERE 4 (GPS with compass and barometer)
- 4 x T-Motor V80A (ESCs with telemetry)
- SKYE 2 DroneCAN (airspeed)

The 4 ESCs have active telemetry (rpm/voltage/temperature/current):
The multitude of active sensors doesn't prevent the RX and TX from working in Mavlink, but the RX froze with a purple LED, unable to communicate with either the FC or the TX.
I turned it off and on again, and the link was re-established.

## Possible Solution (Not obligatory)

Honestly, I don't know how to solve it.
Certainly by eliminating sensors, but then I'd also eliminate ELRS in this setup due to this limitation if there's no solution.

## Details

For days I have been testing the system in "Normal" and not in "Mavlink" and the firmware on the rx has never crashed.

## Your Environment

- TX hardware: Radiomaster TX16S MK3 MAX
- RX hardware: RadioMaster XR4 Dual Band True Diversity RX
- Handset model:
- OpenTX version (including nightly number): 2.12.2
- ExpressLRS version (TX & RX MUST MATCH): 4.10 Official
- Packet Rate: XBand
- Telemetry Ratio: 1:2
- user_defines:

The report names the Mavlink telemetry path and the RX firmware but no source file, test, or entry point. Start by reproducing the freeze with the listed sensor-heavy hardware and compare it with Normal mode. Done means identifying and fixing the telemetry condition that stops the RX, then confirming the link remains responsive under the reported setup.

Written by the indexing model from the issue text.