What you're talking about is channel bonding. That won't do what you're describing however. Bonding like this combines 2 NICs together so that they're combined into a unified NIC device which is then assigned a single IP address.
To do what you want you'd need to either do it using traditional routing rules, setting things up so that all the traffic designated for the WiFi would be routed through the device based on the IP addresses you want to favor this device. Everything else would be routed via your system's default gateway (GW) in your routing table to the Ethernet NIC.
NOTE: The above can be accomplished with the
ip route commands.
An example of what you'd want to do is discussed here in this SF Q&A titled: How to route different traffic thru different network interfaces (Windows). Recognize that these commands are showing how to do the setup using Window's
route command which has different command line switching than the Linux version. The approach is however what you want, so they could be adapted to the Linux equivalent
ip instead of
route command is however considered deprecated and so going forward the
ip command (part of the
iproute2 packages) should be used instead.
excerpt Linux route command
In Linux distributions based on 2.2.x Linux kernels, the ifconfig and route commands are operated together to connect a computer to a network, and to define routes between computer networks. Distributions based on later kernels have deprecated ifconfig and route, replacing them with iproute2.
You can read about advanced routing techniques here in this tutorial titled: Two default routes.