Traditional QoS has been known to be broken for years, and it's something Asus isn't interested in fixing since they consider everyone should be using Adaptive QoS instead.
I know (broken is relative in reality), but you made it working in 380 and it's there in 384 but there seems to be some small changes in the background (for example chain QOSO0 and QOSO1 in 380 dual wan, now only one chain QOSO in 384 dual wan) which maybe could be fixed without great efforts, that's why I want to help.

Adaptive isn't working for my scenario, I need traditional and vpn both working together. Btw, they work fine each alone, so maybe just a litte screw to turn?
Edit: Think I found the cause for this problem: I have a last rule "any protocol -> lowest priority" and if this is present incoming vpn stalls. If I remove it or change from lowest to low vpn works. So maybe a problem with classifying traffic into lowest priority? I'll dig further as long as my knowledge is enough to dig.
Edit2: It's definitely the classification, whenever this is present vpn stalls:
iptables -t mangle -S QOSO
...
-A QOSO -j CONNMARK --set-xmark 0x5/0x7
-A QOSO -j RETURN
As soon as I change it to 0x4/0x7 (equal to low instead of lowest in gui) everything is fine. I classified all other traffic to lowest to check if there is something wrong with lowest priority but http/ftp/... still works fine classified as lowest, only vpn won't work. Now that I know it I can edit my rules and use traditional qos and vpn together. But if someone has an idea how to fix it within the binaries it would be fine.
Regards,
Chris
Edit 3: Gave up now, will try to get rid of traditional QoS and use adaptive instead.