Correct, we have no way of knowing what other community members (or staff) are up to if they don't tell us something. I don't recall having read anything about this lately, so I would doubt it.
Regarding the technical feasibility, pretty much anything is possible, but some things may require an "in the middle" solution (HomeBridge is one example; it's not that Hubitat can't integrate with HomeKit, but you need a HomeBridge server in the middle because Hubitat's current architecture does not permit you to write something that can act in this capacity.) It looks like you would need something like this for local Tuya given the issue with unsolicited inbound UDP.
Sometimes, we get surprises. For example, MQTT also required an "in the middle" solution for the first year and a half or so of Hubitat's existence, then we got a built-in interface (something available to drivers, not a built-in client per se on Hubitat--but now entirely possible without an external system). It's possible we could get similar enhancements to the existing UDP support--but again, we have no way of knowing right now (but I wouldn't count on it soon).
In the meantime, if you have Home Assistant set up already, there is a community solution to get HASS devices into Hubitat (and a custom component on HASS for the other direction), or I suspect that you could probably also do this if you're able to get these devices into Node-RED (which technically doesn't require any custom code on Hubitat, just Maker API). Might be easier than waiting/hoping.