It really depends on the amount of requirements you are managing. Capella is not a requirement management tool, I guess you are aware you would not have the same features in Capella than in Doors. If you need to related your user requirements to things that are not in Capella (V&V procedures, JIRA defects, etc.) than you will not be able to do that from Capella.
If ever these are not issues, then yes, you can use Capella as a reference for your requirements. You will be able to create traceability between requirements and model elements as well as traceability between requirements in different engineering perspectives.
But in that case, you should still use the dedicated Requirement add-on because the native Requirement elements in Capella are obsolete. See the documentation of the add-on:
Capella provides “native” requirements elements(Right click, Add Element “Requirement Package”), but there is no relation with the Requirement add-on. In a next Major Release (not planned yet), these “native” requirements will be removed from Capella and migrated to this new Viewpoint requirements through a dedicated migration tooling and, then, no more available within Capella core.