Do MySQL limitations apply to MariaDB as well on AWS RDS
Short answer:  Probably yes.
Long answer:
I reviewed that link.  All three (MySQL, MariaDB, RDS) are derived from the same original code.  As far as I know, all three have, or at least had all of those bugs/issues/etc.  When one of the 3 fixes a bug, the others may eventually pick up the fix.
For innodb_buffer_pool_instances, MariaDB seems to be leading the change:  MariaDB-10.5.1 changelog says that innodb_buffer_pool_instances deprecated.
WHERE indexed_col1 = 'value1' AND indexed_col2 = 'value2' -- This is almost certainly fixed by using a composite index rather than depending on index merge.
The 10x for blobs was a workaround that was mentioned in 5.6(?).  It may be relaxed in some later version.
lower_case_table_names is a kludge to porting to both Windows and Unix.  It got worse with 8.0's Data Dictionary.  So, beware of switching OS's
As for the 16TB limit for an InnoDB table, I thought it was 32TB or 64TB.  It won't be long before someone finds out for sure.
Lower limits such as 2 TB, and long ago, 2 GB are probably dictated by the underlying Filesystem on the Operating System.
long_query_time allowed microseconds long ago, in 5.1.21, before MariaDB forked off.  I don't understand why AWS mentions it.
My list of limits:
http://mysql.rjweb.org/doc.php/limits