[Closed] .htaccess getting overwritten by WPML causing a redirect loop which crashes the site with HTTP 500 s...

Background of the issue:
We identified the WPML plugin to be the cause of a HTTP 500 server error due to a redirect loop that happens after WPML overwrites the .htaccess file in WordPress. This is the altered Rewrite declarations most likely done by WPML on the .htaccess file that was identified during the 500 server error:

# BEGIN WordPress
# The directives (lines) between "BEGIN WordPress" and "END WordPress" are
# dynamically generated, and should only be modified via WordPress filters.
# Any changes to the directives between these markers will be overwritten.

RewriteEngine On
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
RewriteBase /es/
RewriteRule ^index.php$ - [L]
RewriteRule ^en/wp-login.php /es/wp-login.php [QSA,L]
RewriteRule ^es/wp-login.php /es/wp-login.php [QSA,L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /es/index.php [L]

# END WordPress

This is the normal WordPress Rewrite declarations which are saved on .htaccess file when the site is running ok:

# BEGIN WordPress
# The directives (lines) between "BEGIN WordPress" and "END WordPress" are
# dynamically generated, and should only be modified via WordPress filters.
# Any changes to the directives between these markers will be overwritten.

RewriteEngine On
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
RewriteBase /
RewriteRule ^index.php$ - [L]
RewriteRule ^en/wp-login.php /wp-login.php [QSA,L]
RewriteRule ^es/wp-login.php /wp-login.php [QSA,L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]

# END WordPress

There is a WPML faq (https://wpml.org/faq/why-is-htaccess-getting-overwritten-with-the-language-folder-on-my-wpml-website/) where this issue is discussed but we are not sure if the workaround mentioned is the correct fix for our problem. Everything on the website is updated and this error occurred also before updating to the last versions. As a consequence of these server errors that keep happening, we have to disable the plugin as recommended by the hosting support. But we would like to have WPML support to fix this error if possible before changing to another translator plugin. Link to a page where the issue can be seen: hidden link

Symptoms:
A HTTP 500 server error message due to a redirect loop caused by WPML overwriting the .htaccess file. The error affects all site pages except the homepage.

Questions:
What is causing WPML to overwrite the .htaccess file and create a redirect loop?
Is the workaround mentioned in the WPML FAQ the correct fix for this issue?
How can we prevent WPML from causing this redirect loop and HTTP 500 server error?