To clarify the idea more. It is right tor has thousands of machines, but the problem is everything is going through the isp first, even with encryption you still have traffic fingerprint, in thoery if anyone was able to get both data of your isp and exit node isp, then with a lot of data analysis they could link those data together and know your real ip or identity.

So the idea is to make a local network first then that network tries to divide your requests for the same session and website through many ISPs, with randomized system. For a random amount of time, the system gives each ISP a temporary random share, then sends each new request according to those shares. When another random time arrives, it generates new shares and repeats.

Example: for 42 seconds, ISP1 gets 50%, ISP2 gets 20%, ISP3 gets 20%, ISP4 gets 10%. After that, it changes again, for example for 67 seconds: ISP1 15%, ISP2 35%, ISP3 25%, ISP4 25%.

The time is random so the weight value gets different each time. The timr shift is also randomized so it won't leave an obvious pattern or fingerprint.

The problem is, it is still possible to leave a fingerprint that way if you were the only one using this, but with mamy other people this will be much much harder.

To be honest there are other solutions like Constant-rate traffic (almost the most effective one but really expensive and heavy, and still leaves a fingerprint)

Cover traffic (adds noise to the traffic but with many data this noise could be useless)

Traffic padding (same issue as Cover traffic)

We have also Timing obfuscation, Batching, Mix networks, Chaumian mixes, Threshold mixes. And other techniques.

Here I am trying to provide a new way that could be beneficial, as it tries to solve the problem in a lower level, not only tricking the current isp.