They're mostly separate entities now so it shouldn't affect it directly. This is really bad for image though.
It's still possible for stuff in cyanogenOS to affect cyanogenMOD because they share the same common "bits" (cm skin/changes/tweaks/settings to the OS, launcher etc, has to pass google CTS)
the difference between the two, in case people don't know
cyanogenOS (the commercial version with proprietary libs/apps, not open source, is maintained by paid people on the CM company) is shipped officially on some phones (OPO, micromax,...), has google apps pre-installed, HAS TO pass Google CTS
cyanogenMOD is the open source community-driven version. Some developer in the community (not paid, doing in his/her free time) ports/builds/maintains a ROM for a device. cannot include google apps by default, doesn't have to pass Google CTS, so you have a new build every day or compile a build yourself)
my thoughts: cyanogen has a specific brand. it appeals to end-users/developers/people-who-tinker due to the fact that it's open, can be modified easily, frequent updates etc.
if you try to officially put cyanogen bits onto a phone, a lot of those things change...
people who buy a cyanogen phone because they have heard of the cyanogen brand, and expect that same level of "openness" -> will be disappointed
people who buy a cyanogen phone, but haven't heard of cyanogen brand (and don't care)-> what difference does cyanogen make to them versus a HTC sense skin or Samsung touchwiz skin?
you see similar struggles/problems/difficulties in companies whose product has a dual-license (open source/free vs paid/paid-support) ->
RHEL
But if they can get through the growing pains I could see the CM OS beating Windows Mobile in marketshare within five years.
It'll be hard..
A) Google is moving a lot of stuff in
AOSP back into closed sources/apps. CM will have to replicate all of that
B) No android forks if
you join Open Handset Alliance or have other agreements with google.
more reading material
You left out Google's licensing agreements with hardware manufacturers, which prohibits them from shipping incompatible (read non-GMS containing) Android devices based on AOSP code AND GMS devices. Basically, a hardware OEM will have all GMS applications rejected if they build an AOSP-based device for a different software vendor. Amazon has had to shop around a *lot* to find an OEM for the Kindle - it has to be an OEM with no ambitions of becoming their own Android brand.
Amazon is trying with their Amazon-ecosystem. Samsung is trying with their Tizen-ecosystem. not much luck...
I won't use CM Roms anymore, but that is because I am sick of hacked together Android OSes. I have learned the hard way only OEMs have the access to build stable and feature complete OSes for their devices, and so I would rather reward companies that do that instead of buying devices for their hardware and hoping someone can hack together a CM ROM on XDA.
or get a nexus phone where the custom ROMs are usually stable because AOSP is used to directly build the official ROM, and the custom ROMs modify the AOSP information
i have a nexus 5 because I value that.... (over a removable battery, microSD, better camera)