Sort simulator dependencies into standard, documented and private
To judge whether a simulator plug-in (VPI/DPI capture library) is portable, list every interface it uses and put each into one of three classes: (A) IEEE 1800 VPI/DPI, (B) a vendor interface that is documented in a normative vendor reference, (C) private or undocumented, such as exported internal symbols or fixed offsets. A symbol that resolves with dlsym, or a run that passes, does not make an interface class B; without a documentation citation it stays C. Check that the version guard runs at load time before any private access, not only when the library is built. A library built against one release can still be loaded under another. Also count the one-time per-design work (generated manifests, design-specific glue) separately from per-cycle costs. That work is usually the real barrier to load-and-run on new RTL.