My network consists of the following layers..
The core layer is basically my handoff to our ISP's MPLS Fiber.
Distribution consists of routers, firewalls, bandwidth controls, and other network resources such as: DNS, MAIL, etc.
At the distribution layer's WAN router(s) (connecting to the core), is where I implement Network wide based traffic controls. Much like what you're trying to do with HTTP, VOIP, P2P, setting up queues and priorities for these types of traffic.
The access layer consists of my PPPoE Access Concentrators. Using mikrotik as the PPPoE server, and RADIUS simple queues are dynamically generated when the user logs in to reflect the subscription level of the customer. The WAN ports of the access concentrators connect to the distribution layer routers/switches.
You're trying to do all of this one device, which I don't think you can do because simple queues I believe override the Queue Tree. You may want to refer to the documentation.
It's possible to do a nested tree heirachy on a single device... creating a tree for PPPoE users, hotspot user, etc assigning them to their respective interfaces and nesting the various protocol and priorities underneath it. In my opinion it's not very scalable. What if you want to offer more than a single speed tier to your customers?
Adding the extra layer in the network gives you more control to firewall/shape bandwidth at the desired layers. If you got it working using another method great, this is just my two cents.
The screen shots don't really give enough information on your queue setup, it'd be better to do a
and copy/paste the info here to see exactly what you've done.