Pilot reported an NMAC event while on ATC vector under Class B 4;000 ring at assigned altitude of 3;000 feet. Pilot took evasive action to avoid a collision. Pilot indicated ATC assigned route and altitude was conducive to VFR traffic conflict.

Narrative

I was being vectored from ZZZ to ZZZ1 to the south and under the ZZZ2 Class B 4;000 ring at 3;000 feet. There was converging VFR traffic apparently not talking to Approach at 2;500 feet. The Controller turned me from a 250 to 270 heading which; according to my TCAS; indicated a convergence with the VFR traffic. As we converged; the VFR traffic began to climb as indicated by TCAS. I did not see the traffic. With the traffic at my location and 200 feet below; I began an immediate ascent to 3;400 feet. I received an urgent traffic alert on my TCAS. The location of the incident was just to the south of the 3;000 feet Class B ring. Pilot provided the following reasons why the routing was not the best route. On short flights from the east to ZZZ1; as a turbine aircraft; I am usually vectored over ZZZ2 in Class B. This avoids a large amount of VFR traffic ordinarily present between ZZZ3 and ZZZ1. I question the Controllers decision to vector me at a low altitude through a swarm of VFR traffic on a clear day. The Controller was not talking to the VFR traffic 500 feet below me and should not have vectored me toward the traffic knowing that the traffic could ascend to my altitude of 3;000 feet without even a radio call. Even if vectoring me south; the Controller could have given me a veil of protection from VFR traffic if he had routed me through the 3;000 feet Class B veil instead of putting me under the 4;000 feet veil in Class E.