Support multiple path(or link), aggregate them to one virtual tunnel

A server or client machine may have multiple IP addresses, that means, you can reach your server via multiple paths(or links), if you can aggregate these links to one virtual path, you will speed up your tunnel, and get a stable tunnel if implemented failover.

The following alternatives are not easy to use, they are written in C, you need root to run it, and doesn't work in Windows:
Linux Kernel implementation of MultiPath TCP (MPTCP)
Glorytun is a small, simple and secure multipath UDP tunnel.
MLVPN - Multi-Link Virtual Public Network

To implement this feature, chisel should use config file to config the paths, the client side config may look like:

[vpaths.ssh]
protocol = "tcp"
bind = "127.0.0.1:2222"
forwardto = "127.0.0.1:22"
failover=true  # if not all paths are failed, the virtual tunnel connection will keep
balance = "weight"          #  (optional [weight]) "weight" | "leastconn" | "roundrobin" | "leastbandwidth"
auto_retry=true  # if a path failed, try to connect automatically
[vpaths.ssh.path0]
server="https://1.2.3.4:443/path"  # chisel server side entry 1
if="eth0"  # on client machine , chisel use eth0 to connect to https://1.2.3.4:443/path
weight=6
[vpaths.ssh.path1]
server="https://4.3.2.1:443/path"  # chisel server side entry 2
if="ppp0"  # on client machine , chisel use ppp0 to connect to https://4.3.2.1:443/path
weight=4

If chisel support multi-path, and made it easy to deploy, this would be an awesome feature.
Though it's a challenge, the effort will be worth.

The issue names no files, tests, or entry points; begin by tracing chisel's client configuration and tunnel connection handling. Done would mean supporting configured multiple paths with aggregation, balancing, interface selection, and failover as described, including Windows compatibility.