Cactus covered most of the ASIO driver limitations.
I am not familiar with the Boss unit but what may be preferable is if it has an audio output then send that to your main interface if you want to record from that in realtime which would allow you to continue using ASIO. Your Boss would still be greyed out though in Prefs and you would lose an audio input on your interface to hook it up to (or two if it's stereo output?).
For some devices (and I'm guessing this won't apply) that have "Optical/ADAT" in puts/outputs you can daisy chain the units. eg: My old PCI Layla 3g's breakout box has both optical/ADAT in AND out connectors. My Focusrite Scarlett 18i6 has and optical/ADAT input (no output though). With a proper optical cable I can run the optical output from the Layla's breakout box into the optical input on the Focusrite box and have access to the extra analog inputs on the Layla on TOP of the inputs on the Focusriteand remain in ASIO mode (there are some channel limitations/considerations but it does indeed increase my physical input count).
Just some (probably not helpful to this situation) rambling.
As for the alternate Windows audio drivers Cactus mentioned... yes they are (or at least have in the past) definitely more latency/glitch prone than dedicated ASIO drivers. However Win10 has supposedly improved these audio drivers and intends to continue working on them which will allow us to use multiple devices more reliably. I do not yet own a Win10 system to test this on but the Bakers apparently have and the results were positive.
In the (hopefully) very near future I will have a system to test such things on and of course will blather on about the results once I do.
Cheers.