Actually, SAP does not differentiate the scenarios technically, but based on the business scenario the application will be used for (which can actually determine the workload with a higher precision than the technical architecture the application is based on).
If you check the same note you've linked, it list several products that are technically based on NW AS ABAP and that can coexist with BW's ABAP stack, namely:
- SAP Customer Activity Repository (CAR)
- SAP Customer Engagement Intelligence (CEI)
- SAP Tax Declaration Framework (TDF)
- SAP Landscape Transformation (SLT)
- SAP Fraud Management (FM)
- etc.
Hence, it is technically possible, even in production, to deploy 2 AS ABAP stacks pointing to the same HANA DB instance (albeit, in separate DB Schemas), given that those applications are included in the white list concomitantly.
Similarly, SAP has released another white list note with the list of HANA applications that can coexist on the same HANA DB as other Business Suite applications (ERP, CRM, etc.). This SOH white list is present in SAP Note 1826100. It includes most of the same apps the standalone white list includes, such as CAR, CEI, FM, TDF, among others. The good thing about this deployment is that, since most of these apps would rely on Business Suite data (mostly ERP & CRM) to run, being deployed on the same HANA DB, they can natively consume logical views on top of the transactional data from the other DB Schema, without requiring a SLT/DS replication (simplification, anyone? 
).
So, if you think about it, what ABAP-based products are not authorized to be deployed together? Basically, everything else that was not mentioned in those two notes, most notably:
- Business Suite apps & BW (e.g. two separate ERP & BW instances on the same HANA DB)
- This is not to be confused with the Embedded BW case, where the BW models reside in the SAP_BW component that exists within the ERP ABAP stack. In this case, since typically the models will be virtual models (i.e. no data acquisition / extractors would be required), the BW workload is considerably lower than in a separate BW instance, allowing it to share the same infrastructure than ERP. BTW, this is the BI architecture that sFIN is leveraging (and that will probably be there for the rest of sERP as well).
- Business Suite apps with other Business Suite apps (e.g. two separate ERP & CRM instances on the same HANA DB).
Specifically to tackle that second point, from Business Suite 7 innovations 2013 onward (ERP 6.0 EHP7+ & CRM/SRM/SCM 7.0 EHP3+, i.e. based on AS ABAP 740+), SAP has introduced the possibility to deploy SRM & SCM* as add-ons to the ERP ABAP stack (of course, this introduces all the complexity of doing shared-infrastructure ALM, i.e. planned maintenance windows must match, unexpected downtimes will impact each other etc.).
Hope that helps.
Best regards,
Henrique.
* I haven't read all the details, but I'd suspect SAP only allows the co-deployment of ERP & SCM for non-APO SCM components, since LiveCache would add a huge deal of complexity to the workload management between the two applications. But that's just a hunch (though, even if allowed by SAP, I wouldn't recommending co-locating ERP & APO together on the same infrastructure, due the heavy workload nature of both applications).