Wrong query optimization plan with InnoDB

Question

After switching DB engine from MyIsam to InnoDB on MariaDB 10.3.39 we noticed endless queries and huge disk space usage. The problem are some queries that are wrong optimized with the new engine.

Example:

explain SELECT table1.id, table1.column1, table1.column2, table1.column3, table1.column4, table1.column5, table4.column1, table3.column1, table3.column2, table3.id, table2.id, table2.column1 
FROM table1 INNER JOIN table2 ON table2.id = table1.table2_foreign_key INNER JOIN table3 ON table1.table3_foreign_key = table3.id INNER JOIN table4 ON table1.post_id = table4.id 
WHERE table3.column3 = '0' AND table1.table3_foreign_key NOT IN (1,18,25,28,30,38,55,84, 31) 
ORDER BY table1.id DESC LIMIT 3;

When using MyIsam the optimization path is correct and the query ends in milliseconds

+------+-------------+--------+--------+-----------------------------------------+---------+---------+---------------------------+------+-------------+
| id   | select_type | table  | type   | possible_keys                           | key     | key_len | ref                       | rows | Extra       |
+------+-------------+--------+--------+-----------------------------------------+---------+---------+---------------------------+------+-------------+
|    1 | SIMPLE      | table1 | index  | PRIMARY,table2_foreign_key,idx_sortable | PRIMARY | 4       | NULL                      |    3 | Using where |
|    1 | SIMPLE      | table2 | eq_ref | PRIMARY                                 | PRIMARY | 4       | table1.table2_foreign_key |    1 |             |
|    1 | SIMPLE      | table4 | eq_ref | PRIMARY                                 | PRIMARY | 4       | table1.id                 |    1 |             |
|    1 | SIMPLE      | table3 | eq_ref | PRIMARY                                 | PRIMARY | 2       | table1.table3_foreign_key |    1 | Using where |
+------+-------------+--------+--------+-------------------------------------+---------+---------+-------------------------------+------+-------------+

but with InnoDb the optimization path is completely wrong: it creates a huge temporary table and sorts it, ignoring that it should be possible to do that only with primary keys and that the result needs only 3 rows. The query lasts hours.

+------+-------------+--------+--------+-----------------------------------------+------------------+---------+---------------------------+---------+----------------------------------------------+
| id   | select_type | table  | type   | possible_keys                           | key              | key_len | ref                       | rows    | Extra                                        |
+------+-------------+--------+--------+-----------------------------------------+------------------+---------+---------------------------+---------+----------------------------------------------+
|    1 | SIMPLE      | table2 | index  | PRIMARY                                 | idx_popular_last | 15      | NULL                      | 5389158 | Using index; Using temporary; Using filesort |
|    1 | SIMPLE      | table1 | ref    | PRIMARY,table2_foreign_key,idx_sortable | post_thread_id   | 4       | table2.id                 |       3 | Using where                                  |
|    1 | SIMPLE      | table4 | eq_ref | PRIMARY                                 | PRIMARY          | 4       | table1.id                 |       1 |                                              |
|    1 | SIMPLE      | table3 | eq_ref | PRIMARY                                 | PRIMARY          | 2       | table1.table3_foreign_key |       1 | Using where                                  |
+------+-------------+--------+--------+-----------------------------------------+------------------+---------+----------------------------+---------+---------------------------------------------+

We've already found different queries with this problem and we solved it using SQL-Hints "force index(PRIMARY)" on table1, but we would like a global solution to fix all possible problematic queries at once. Something like a server configuration to disable temporary tables during SELECT or to bring the behaviour of InnoDB-Optimizer as it was with MyIsam.

Thank you in advance for suggestions