OK, best I can tell you is that I go after results I want to see and if then something stands in my way, I call it a bug and I raise some noise over it.
It is a public secret that Fusion is in development and has many issues that need attention from a development point of view,.. and someone is banging their head against the wall to catch up with all of our pissing and moaning.
The good news is that there is progress and we are not paying $20000 for using whatever is functioning.
I can list dozen bugs in turning that are still there but I can also get around them and get things done every day.
On subject of sharing experimental files, new users in particular tend to list page full of stuff and upload pictures but don't share Fusion file.
It is very annoying to read all that and forget what was at the top of it by the time you read last sentence when best and most effective way to get someone to engage in figuring things out is to upload Fusion file.
Sorting thru dozens of settings and connecting dots while only the poster has full information is sort of game that is not very productive for that poster in general.
My file can be altered in many ways to generate problems but only one I cared to mention is conflict in checking two boxes that contradict each other in function, I never produced that extended tool pass and really don't need to look for how or why it occurred in your file or my file under your scrutiny.
Get comfortable with term "workaround", yes we must do the thinking and finding alternative ways to get things done.
So if you focus on getting things done, you avoid those known and newly discovered problems, someone else's job is to study reasons why they occur and coming up with solutions, reporting bugs is as far as user can go.