IonicModule in standalone Angular Component - best practices

When creating a standalone component in Angular, the list of Ionic Components can make the imports and @Component import quite large. Eventually my developers want to replace the list with IonicModule and be done with the individual imports.

The app works either way, so the question is:

  1. What is the best practice?
  2. What is difference?
  3. Am I losing out on tree shaking? Anything else?
  4. Should we be trying to use provideIonicAngular() as well?

Thanks,
Daniel