.. not while there isn't a simple way to autodetect the plugin and run the content.
Voyager can't predict the class id's of windows components, and which plugins are which. They'd at least need to define a mimetype (not on the demo page..) on the OBJECT tag.
You could put the MorphOS objects (or Mozilla plugins etc.) in the same cabinet file, with some pretty references but nobody made a decision on that.
