CTC only makes “templates” available to copy over to the child theme. A “template” is defined as a php file that does not contain functions or classes and can be loaded via the locate_template() function during the front end execution. PHP files that are executed in the admin or as includes during the theme program flow 1) run the risk of causing a fatal error if they are duplicated in the child theme; and 2) can only be included with an explicit file path.
The child theme inherits the parent theme core ( non-template ) code. To customize non-template PHP, you must either add override functions to the child theme functions.php file ( assuming the are “pluggable”, i.e., wrapped in if (!function_exists()) conditional ). The child theme only contains the necessary code for it to work.
If the functions are not “pluggable,” you need to locate the action/filter hooks (if any) that fire at the point(s) these sections are rendered, and create custom callback functions in the child theme function.php file to execute when the hooks are fired.
If the functions are neither “pluggable” nor contain action/filter hooks, then you are stuck with the parent theme functionality. At this point I would consider using a theme that is more extensible.
This is a little more advanced than the typical child theme customization, but with a little trial and error I am sure you can work it out. Please review the following resources for more information.
https://codex.www.ads-software.com/Child_Themes
https://codex.www.ads-software.com/Template_Hierarchy
https://codex.www.ads-software.com/Plugin_API
https://codex.www.ads-software.com/Plugin_API/Action_Reference
https://codex.www.ads-software.com/CSS
https://www.childthemeconfigurator.com/how-to-use/
https://www.childthemeconfigurator.com/tutorial-videos/
https://www.childthemeconfigurator.com/how-child-themes-work/
