I don't know what state the whole patch is, but, at the very least, I'd
expect that patch to export the fact that it's exporting synthesised
data from another driver, so that it can be easily ignored in user-
space that already supports IIO devices.
It does through "Input device name:" starting with "iio-bridge:" as you can see in the commit message of [RFC v3]:
The patch isn't upstream, but it might be worth avoiding binding with those anyway. See: https://lkml.org/lkml/2019/5/10/163