transaction_isolation and binlog_format

[trendless]

I just ran across this in the Nextcloud manual:

Database requirements for MySQL / MariaDB (https://docs.nextcloud.com/server/34/admin_manual/installation/system_requirements.html#database-requirements-for-mysql-mariadb)

The following is currently required if you’re running Nextcloud together with a MySQL / MariaDB database:

• “READ COMMITTED” transaction isolation level (See: Database “READ COMMITTED” transaction isolation level)
• Disabled or BINLOG_FORMAT = ROW configured Binary Logging (See: https://dev.mysql.com/doc/refman/5.7/en/binary-log-formats.html)

Looks like the defaults in ynh MariaDB are REPEATABLE-READ and MIXED, respectively. Are there any ynh-specific downsides to adjusting MariaDB to align with the Nextcloud requirements?