Using Homepage as Community URL Causes Customizer and Course Routing Issues

I’m setting the homepage as the FluentCommunity portal by using:

define('FLUENT_COMMUNITY_PORTAL_SLUG', '');

This works in terms of routing, but it introduces a couple of problems:

1. Customizer Becomes Inaccessible

When the homepage is used as the community URL, the FluentCommunity customizer no longer loads. This means I can’t access the customizer to change FluentCommunity colors or other visual settings.

2. Disabled Modules Still Claim URLs (Courses)

If the Course module is disabled and the homepage is set as the community URL:

• domain.com/courses correctly maps to FluentCommunity courses instead of
  domain.com/portal/courses (which is great).
• However, when the Course module is disabled, FluentCommunity still tries to load the /courses route.

This causes conflicts when using TutorLMS or another LMS, effectively making /courses unusable.

To fully disable the courses route, I currently have to add this workaround:

add_filter('fluent_community/app_route_paths', function ($paths) {
    return array_diff($paths, ['courses', 'course']);
});