SharePoint framework Vs SharePoint hosted add-in, when building CRUD operations

Previously (Early stages of sharepoint online) i use to build many sharepoint hosted add-ins to implement scenarios such as:-

1. using node.js or pure javascript, i build a sharepoint hosted add-in.

2. the add-in integrates with sharepoint lists using REST api.

3. i use this approach to implement some advances CRUD operations that can not be achieved using sharepoint lists' views and forms. something similar to what is provided in this link https://www.c-sharpcorner.com/article/rest-crud-operations-using-sharepoint-hosted-app-office-365-part-two/

but one drawback i have faced recently, is that the add-in will be rendered in the classic experience, and i can not get the add-in to render using modern experience. now i read about this and many folks mentioned the SharePoint framework appraoch, which can allow us to build modern web parts. but from my experience i use web parts to display information, and i never saw a web part which provide CRUD operations. So if i want to provide CRUD operations in modern experience,  then is building modern web parts using SharePoint framework the way to go?

second question. can we force the SP hosted add-in to render using modern experience ?

//Hint. i can not use power apps in my case, as i have external users who need to access the CRUD operations, and currently power apps does not work for external users.

Thanks in advance for any help on my above 2 questions.

Regards