Although it appears the throttle might pose as a problem for AOL proxies, in reality, it works out well.
AOL load balance it's ip extremely frequent to a point where your AOL ip to the end server change every few seconds. This was the case before, not sure if they have changed this policy since.
Even if Lsws throttle a proxy, AOL has tons of proxies to go around to mitigate this effect. When I started to throttle connections, I noticed most of the "offenders" are AOL's cache.proxy which are not crucial to serving the page. Since most of the cache servers are there to save AOL external bandwidth costs, they really are not critical to the end-user's experience. We don't need stinky AOL to do the caching for us. =)