Rebranding GPL software for customers

Sorry for the vagueness upfront...

I work for a company that provides a backend product for which we recommend very well known OSS front end web software for in order to visualize and administer it. There appears to be a desire to customize this OSS software to incorporate our branding, and to limit the other backends that it can be used for in order to help frame that deployment as FOR our back end.

This isn't about removing functionality, just, I think, to ... keep it in our customers minds that this web front end they're looking at is there for monitoring either the backend and / or their data that is IN our backend that they are paying us for.

This feels weeeeeeeeird to me. Outside of the logistics of it, can you see a company saying "thanks for buying our product we recommend you use this (probably outdated!) fork of this industry standard product to connect to it as it has our logos copied into it"?

We used to develop our own in house web front end, but that stopped before I joined, and I guess some people are missing that in some way?