@Frankenhaus No personal attacks or name calling in this forum, we're all better than that.
This forum is neither a place for blindly worshipping Logic Pro, nor a place to bash Logic Pro. Neither is constructive.
Quick recap on what this forum is about.
We are here to help each other use Logic Pro.
When someone brings up an issue, we can collectively put our minds together to try and figure out how to resolve it. If the issue cannot be resolved, we try to figure out the easiest way to reproduce the issue, and report our findings to the software developers in order to help them fix it.
We've offered to have a look at a file that shows an example of the issue you're describing. I've suggested you first make a copy and simplify the file to make it easier on whoever is going to have a look at that file. If you don't want to take the time and effort to do that, you could post your file as is, and sometimes a brave soul is willing to take the time and effort for you!
Simplifying a project file for troubleshooting purposes doesn't imply you should simplify your workflow when actually using Logic Pro, this is just a troubleshooting process.
Allowing others to experiment with an actual Logic project file that displays the issue and trying to remove variables in order to pinpoint the culprit is one of the most efficient troubleshooting methods we've used in the 25 years this Logic Pro community has been active.
When we do not follow any kind of troubleshooting methodology, all that's left is ranting and conjecturing, which often leads to arguing. That's not constructive, and that's not the purpose of this forum.
Let's focus back to the issue at hand.