When a business analyst discovers that different teams have different needs or preferences for using Salesforce fields, they should refine the requirements to accommodate both teams. This is because deleting fields that are actively used by another team could cause data loss, errors, or inefficiencies in their processes. The business analyst should work with both teams to understand their use cases, data models, workflows, reports, dashboards, integrations, security settings, etc., and find ways to customize Salesforce fields that meet both teams' needs without compromising data quality or performance. References:
https://trailhead.salesforce.com/content/learn/modules/salesforce-business-analyst-certification-prep/requirement

Identity Only is the Salesforce standard license that can be given to someone who need access only identity services, such as single sign-on (SSO). Lightning Platform, SSO License, and Salesforce License are not valid standard licenses in Salesforce. References:
https://help.salesforce.com/s/articleView?id=sf.users_license_types_available.htm&type=5

Explanation
This answer points out that the previous VP's requirements may differ from those of the new executive as the largest risk with this approach of using the inherited requirements in lieu of a traditional discovery process for a Sales Cloud implementation. Requirements are statements that describe what a solution must do or have to meet the needs and expectations of the stakeholders or users. Requirements may change over time due to various factors, such as business goals, market trends, customer feedback, or stakeholder preferences. Using theprevious VP's requirements without validating them with the new executive may result in a solution that does not align with their vision, strategy, or value proposition.
References:https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick-look/use