This behavior can be easily reproduced in the test lab.
The key here is to send the e-mail to support with a clear description of the problem, have you done at least that? Because posting it at the forum is not the way to inform Mikrotik about the problem, they don't read every single post at the forum, while they do read every single e-mail which arrives to email@example.com
Sending supout.rif makes it easier (and sometimes at all possible) to analyse for guys at support because they have all the necessary information in one place; what they actually need is the complete configuration including the dynamic elements which are not part of the export (because e.g. a dynamically assigned address may collide with a manually configured one) plus the information about the routerboard model, routeros version, and the actually running version of the firmware. So if your case description is clear enough, the supout.rif may not be actually necessary, but the formal process the support guys have to follow makes them ask for it because the alternative ways of putting the information together cost them more time. So I've found it easier to change the passwords and addresses (or, better, set up an environment with no public addresses) and generate the supout.rif than to argue with them why it is not necessary.
But again, the key is to describe the case clearly enough using the right information channel.
Instead of writing novels, post /export hide-sensitive. Use find&replace in your favourite text editor to systematically replace all occurrences of each public IP address potentially identifying you by a distinctive pattern such as my.public.ip.1.