Is the network contiguous such that Site 2 can be defined within a single subnet range? Unless there's a specific reason for it I don't recommend this kind of load balancing (far more efficient to direct traffic flow to R1 and R2 LAN-side rather than to have them send traffic across to each other and then onto Site 2), but one way is to cut Site 2's IP scheme in half, and use route maps to push all traffic for the first half out Interface A, and the second half out Interface B.
Here's an example config file snip to make a routing policy that puts anything destined for the first half of the 172.16.0.0/16 range onto one interface, and the second half onto the other (replace the loopbacks with relevant interfaces in your configuration):
interface Loopback1
no ip address
ip policy route-map Example
!
access-list 100 permit ip any 172.16.0.0 0.0.127.255
access-list 101 permit ip any 172.16.128.0 0.0.127.255
!
route-map Example permit 10
match ip address 100
set interface FastEthernet0/0
!
route-map Example permit 20
match ip address 101
set interface Loopback0
Since your routing protocol is OSPF, you can't do unequal cost load balancing without hard-coding your metrics, and even then the cost changes on each given interface is globally significant, so it would be difficult to do it for both R1 and R2, for both sites, unless you get really fanciful.
Also if you DO go with EIGRP and do unequal-cost load balancing by changing the variance, I strongly suggest adding "mls ip cef load-sharing full" for per-flow load-balancing. Much better than the default, although I think that syntax has changed a few times. Also assuming you're running CEF.
CCNP, CCDP