Unlikely. As far as I can tell, Safari WebExtensions are built on top of the pre-existing Safari App Extension API. This was likely done so Safari could continue to rely on the macOS App Extension API instead of needing to duplicate all of that in Safari itself.