Thanks for the feedback!
However, it looks like ifupdown2 was replaced by ifupdown accidentally at some point which seems to have caused the issue.
So above stated issue exist on ifupdown, *not* ifupdown2. (Which is strange, I thought vlan-aware-bridges and bridge-vids were introduced with...