Host to user package split up between base and home-manager dotfile

[projectCursed]

I use Hyprland for my desktop but not for my Mac, still I want to share my user to both hosts while having the flexibility of home-manager for multiple users at the same host. My current implementation, which is hard coded, takes much inspiration from this discussion #636. Where I have one file ./modules/aspects/hyprland.nix which contains both a base and user-specific home-manager dotfile configuration, oversimplifying:

{ den, … }: {
  den.aspects.hyprland = {
    base.nixos = {
      # Greetd, PAM, Hyprland flake packages, etc.
    };
    <user> = {
      includes = [ den.aspects.hyprland.base ];
      homeManager = {
        # User specific configuration for Hyprland
      };
    };
  };
}

I am conflicted whether such a file is the right approach, at one hand the dotfile is user-specific where it may be split up, but it is also highly dependent on the Hyprland flake itself to work.

At the same time it is just a part of the issue, I would still need to provide this user configuration to my host. Currently I just provides.<user>.includes from my host. Yet I feel this may be a bit convoluted.

As the cherry on top, I attempted to make my hyprland.nix more modular through declaring the user from greetd as user.userName. Though I have genuinely no idea how to make this happen without inevitable constraints, like what if I have multiple users? Want to decide a specific one? Switch?

I still do not plan to have multiple users, just me, but I thought that a properly separated module system would be easier to maintain in the long term.

I know this is very dense, I have tried to solve this without being a burden. I am very new to all this. Though my search skills coupled with forced upon LLM (which literally gives misinformation), did not help to the extent I hoped for.