Enterprise apps do not have to be associated with a subscription. Azure AD B2C apps model is becoming one with Azure AD apps model. Currently they are pretty similar with some minor differences. Due this you can manage them using the same tools (AzureAD powershell, MS Graph) and use the same SDKs (MSAL, Microsoft Identity Web). Tokens are pretty similar too, take a look to Microsoft identity platform ID tokens, Microsoft identity platform access tokens and Overview of tokens in Azure Active Directory B2C.
The immediate differences when migrating will be the authorization, token and metadata endpoints:
Azure AD
https://login.microsoftonline.com/{tenant}/oauth2/v2.0/authorize
POST https://login.microsoftonline.com/{tenant}/oauth2/v2.0/token
https://login.microsoftonline.com/{tenant}/v2.0/.well-known/openid-configuration
Azure AD B2C
https://{tenant}.b2clogin.com/{tenant}.onmicrosoft.com/{policy}/oauth2/v2.0/authorize
https://{tenant}.b2clogin.com/{tenant}.onmicrosoft.com/{policy}/oauth2/v2.0/token
https://{tenant}.b2clogin.com/{tenant}.onmicrosoft.com/{policy}/v2.0/.well-known/openid-configuration
Also Azure AD B2C applications can only access a limited set of permissions for 2 built in API: MS Graph and AAD Graph (legacy). Azure AD apps on the other hand can request permissions for a bigger set of APIs. For both you can expose and create your own custom permissions.
You can configure and issue custom claims with Azure B2B trough custom policies while Azure AD can issue optional claims and do claims mapping.
Finally, regarding the user info, for Azure AD users and Azure AD B2C local users you can use MS Graph. For Azure AD B2C federated users you will have to use the ones provided by their identity provider.