Nowhere do i see where the QUECTEL EC25-EUX or EC25 series supports SBAS. GPS, Glonass, BDS, Galileo and QZSS etc yes which can be classed under the GNSS umbrella is included for positioning requirements but nothing specifically in regard SBAS which is a whole other series of augmentation systems typically associated with specific or multiple GNSS constellations. Typically SBAS like WAAS, EGNOS, MSAS, QZSS, GAGAN, SDCM, BDSBAS, SouthPAN, WAGE, StarFire, OmniStar etc etc are not global but region specific and not the sort of third party systems one would expect to find embedded in this type of router device, the primary purpose being M2M 3G/4G/5G type data device, limited location device for supplementary options second.
From what I see in the EC25 series specs, No, SBAS is not available, GNSS (different constellations) yes but GNSS by itself is not SBAS and for such a router, SBAS is really beyond the intent.
This device (RUT955 etc) is capable of bridging RTK corrections from third party augmentation systems be they subscriptions or free services etc but that would be in conjunction with additional fit for purpose GNSS hardware, hence where NTRIP comes into play.
In regard the relationship between the CLI NTRIP command and serial device NTRIP output there is no interruption of the serial output by running CLI commands. Again don’t have in-depth background regard CLI commands but have proven CLI does not interrupt serial NTRIP output.
As for NMEA, a once wise person stated, the thing about Standards is, there are so many of them and this is especially the case with NMEA standards and how different parties interpret and implement NMEA and different versions within the standard along with extensions.
$GPGGA is (by the standard) G(P)S Time, Position and Fix related data. There’s also $GBGGA, $GGGGA along with like $GNGGA which simply confuses the whole thing with standards.
For NTRIP $GPGGA and GPS Fix type 1 is totally adequate and fit for purpose and doesn’t waste resources, doesn’t need to.