We probably don't want to add this directly to WRY, since that's focused on hosting system webviews, but if we can implement a drop-in replacement that re-exports the same public interfaces as WRY, then we should be able to integrate this more easily into the rest of the Tauri runtime/framework.
This will likely require multiple sub-issues itself, possibly broken up into a few per-platform.