Is it possible to limit the amount of bandwidth SCCM uses?

I don't care about throttling site-server to client as the clients are seperated by boundries, and the subnets of those boundries are all Gigabit.

I only have one site server, the rest of my site systems are server shares. I've included a screen shot of how my site systems are setup. Basically "Black" is my main site system, and the rest of the site system servers are setup as server shares.

If I setup a "New Standard Sender Address"; is the "site server name" it asks for the name of the server hosting the server SHARE?
Region-Capture.jpg

I tried creating a new standard sender address and found that you can only have one address per site, I guess that makes sense.  

Since I only have one site; would I still setup a "standard sender address", and type in the name of my primary site server (black)?  

The bandwidth issue I'm having only happens when Black replicates to the other "server shares" on remote DP's. BU, CC, DO, etc are all DC's with shares setup for SCCM.So when "black" copies a package to "AC", it uses up all my available bandwidth. Is this a client BITS setting?

I htink I found something else, under "client agent properties" there is a setting to enable BITS for DP's only; is this what I need to configure?
Region-Capture.jpg

So what exactly does the above screen shot do for throttling network traffic?

As far as seconday sites are concerned, I kind of figured that this is where things were going to lead. I have a couple questions regarding that though:

1) Some of my remote sites are VERY small (>10 Pc's); would these locations be good canidates for "Branch Distribution Points"? If so, can I make the DC on those subnets the "BDP"?

2)  Can I have BDP mixed in with seconday sites? So I would end up with my Primary Site (Black) communicating with my seconday sites and my branch distribution points; would this work or should I just make every location, even my small ones secondary sites?

All I'm trying to accomplish is bandwidth throttling between my DP when I sync Microsoft Updates and other software packages. If doing all this extra work will SOLVE my isssue and accomplish what I want, then I will do it. I just want to make sure I'm not doing all this extra work for nothing.

Oh, I forgot to add that I already established SCCM site boundaries based upon my Active Directory IP subnets, define my IP subnets and sites in Active Directory and useed the AD sites to create boundaries in SCCM.

Can a Secrondary Site system be a DC? That is the only server I have available at my remote locations, our DC would be our Secondary Site. Is this support, a good idea?

I think I posted the question in the wrong zone, therefore I didn't get many responses. I'm going to repost this.