I think it comes down to how you are deploying currently and how that process can be extended. As you state, using the portal's 'import' functionality is just an automated method of creating an API in APIM which references the backend function. This is a 'point-in-time' view and, while there now appears to be a link between the backend API and the API definition in APIM, it is not a dynamic link - just an imported API based upon specific definitions of the back-end, named-values etc. So, if you update your back-end with a new endpoint then you need to add this manually in APIM (or potentially re-import). What you need to do is create a process that dynamically updates the API management front-end endpoints for your API when the code changes and a new endpoint is added / something is changed.
You mention use of CI/CD. Take a look at this article. It uses YAML CI/CD pipelines to generate an OpenAPI definition of the API (In the article's case it is a webapi) from the startup assembly as part of CI, and then uses this OpenAPI spec to then update the API management instance as part of the CD stages. It may be an approach that you can adopt to achieve what you are looking for.
automating-your-openapi-updates-to-api-management-through-your-cicd-pipeline
Good Luck!