According to the description in MDEV-17554,

It is assumed that one DML command will not generate history rows more
than specified LIMIT. Otherwise history would overflow generated
partition, a warning would be printed, and user action would be
required to rebuild partitions

There is no warning.

In the test case below, the limit is 1000, and each DELETE moves 1200 rows into a historical partition. It is done twice in case of the first DELETE doesn't produce a warning due to MDEV-25475; but the second one does not do it either, neither in the client nor in the error log.

MariaDB [test]> create or replace table t (x int) engine=MyISAM with system versioning partition by system_time limit 1000 auto;

Query OK, 0 rows affected (0.038 sec)

MariaDB [test]> insert into t select seq from seq_1_to_2500;

Query OK, 2500 rows affected (0.010 sec)

Records: 2500  Duplicates: 0  Warnings: 0

MariaDB [test]> delete from t limit 1200;

Query OK, 1200 rows affected (0.011 sec)

MariaDB [test]> delete from t limit 1200;

Query OK, 1200 rows affected (0.037 sec)