The deprecated and new BICC View Objects is listed in the "IMPORTANT Actions and Considerations" section of the Oracle Fusion Cloud Common Technologies and User Experience What's New document

PVOs aren’t specific to BICC—they’re used across Fusion Applications within Oracle Application Development Framework (ADF). Deprecation of PVOs may not immediately disappear in the BICC UI because they can still exist in ADF. BICC typically announces PVO deprecations ahead of their removal from ADF. Once they are…

Another comment on extract vs. nonextract PVOs. The nonextract PVOs are used throughout Fusion Applications just not OTBI/BICC. They contain a lot of columns that are required outside of "reporting". The extract PVOs are scaled down to only include columns deemed required for reporting purposes.

If the VO is marked as customized then changes made by Oracle to seed data/starter selections will not get included in extracts. Best practice would be to edit/close (touch, don't need to actually make a change) to get the VO marked as customized. That way any changes coming from Oracle will not affect your extracts/jobs.