Load Balancing to Only One Pool Member

I have an issue where all traffic in a pool is going to the fifth of 5 pool members. We are using cookie persistence and I know there can be issues with that. We are also using both an http and OneConnect profile. From the sols and DC articles I've read it seems like the problem will arise if you do NOT have a oneconnect profile assigned. I have tried pulling http/oneconnect/tcp profiles on and off, using default profiles. The only thing I haven't tried is falling back to source address persistence. That is a last resort I do not want to use. Due to the application architecture source address persistence will definitely result in uneven load. All the "custom" profiles are built from an F5 guide for the application (Epic HyperSpace Web; Link to Guide). That being said this config seems pretty straight forward, but any help would be very much appreciated. We have captured traffic and seen the cookies present in the sessions.

Below is the config.

ltm virtual /PARTITION/v_80 {
    destination /PARTITION/10.10.1.1:80
    ip-protocol tcp
    mask 255.255.255.255
    persist {
        /PARTITION/Custom-cookie {
            default yes
        }
    }
    pool /PARTITION/pool_80
    profiles {
        /PARTITION/Custom-OneConnect { }
        /PARTITION/Custom-http { }
        /PARTITION/Custom-lan-optimized { }
    }
    source 0.0.0.0/0
    source-address-translation {
        type automap
    }
    translate-address enabled
    translate-port enabled
}

ltm pool /PARTITION/Pool_80 {
    description "HTTP Pool"
    load-balancing-mode least-connections-member
    members {
        /PARTITION/001:80 {
            address 10.1.1.1
        }
        /PARTITION/002:80 {
            address 10.1.1.2
        }
        /PARTITION/003:80 {
            address 10.1.1.3
        }
        /PARTITION/004:80 {
            address 10.1.1.4
        }
        /PARTITION/005:80 {
            address 10.1.1.5
        }
    }
    monitor /Common/http_head_f5 
    service-down-action reselect
}

Only change to custom oneconnect profile is mask is 255.255.255.255.

Only change to tcp-lan-optimized profile is the idle timeout is set to 1200s.

Only change to http profile is that 'Redirect Rewrite' is set to Matching.

Custom cookie persistence uses default settings.