Yes, that thread that you pointed out can show how dangerous it is to set RTH higher than max altitude, thanks for that link!
Sorry but I think you are misunderstanding both my post and more importantly that thread.
With regards to the thread, the drone launched under an air corridor. The floor of that air corridor was at 196.9ft, 60m, AGL.
This is the height shown at the start of the log of that flight, in the "HOME.heightLimit [ft]" column.
The pilot had previously set a height limit of 213.3ft, 65m, in the app.
As soon as the drone flew out from underneath that corridor the log switched from showing the height limit as 196.9ft to 213.3ft, why? Because the latter was the height that the pilot had set.
It was the presence of the air corridor that reduced the max height shown in the log, that reduced height was also applied to the drone, and in so doing this prevented the drone from climbing through the floor of the air corridor.
An aside.
RTH height CAN NOT be set higher than the user set maximum height, the app simply will not allow that.
I wrote about that in post 2 of that thread.
I had previously experimented with sending the drone up to 'height' with the RTH height being set to near the maximum height setting. I then reduced the maximum height setting in the app, to below the drone's current height, and the drone was forced downwards to comply with the new setting. The RTH height was also reduced such that it was equal to the new maximum height setting.
Getting back to that thread.
The RTH height shown in the log, in the column HOME.goHomeHeight [ft], was constant the whole way through the log, at 213.3ft.
The drone was flown out to sea, beyond the air corridor, and eventually an RTH was triggered whilst the drone, a
mini 3 pro, was still well away from the air corridor. The drone climbed to the set RTH height of 213.3ft and flew towards home.
It ran into the side wall of the corridor and got 'stuck' there (pilot error ?).
It ran out of battery and entered a forced landing but once the drone was below the floor of the corridor the pilot was able to move it towards the home point and safety.
Since it is impossible to set the RTH height higher than the user set maximum height setting, the fact that the RTH height was shown, at the start of that log, as higher than the user set maximum height showed the presence of an air corridor.
With regards to your flight.
If you did not change the height settings then something else did, the only thing that I know of that can do that is the floor of a restriction-zone/air-corridor but others might know of other things that can.
If you happened to have had the RTH height set to more than 24m then I am suggesting you should check the values shown in the columns "HOME.goHomeHeight [ft]" & "HOME.heightLimit [ft]" in the Phantomhelp CSV of the flight log and, at the start of the log, see whether or not the former is higher than the latter.
If so then I think there is some form of restriction zone above the house.
Alternatively you might be able to PM the .txt flight log to me and I will have a look.
Oh, forgot, Suren's flight and log in that thread demonstrates that some drones now have programming that makes them descend to fly under an air corridor if that corridor would otherwise block the RTH path.