How to properly publish two similar applications in google.play?

Question

Android

Good afternoon.
I want to say right away: I know that there are developers who publish the same applications in batches, changing only the icon - this is not my case.
I have an android application in google.play, it is published only in the Russian segment of google.play, it is in Russian.
I am making another app with the same functionality + a few new features, with a slightly different design, but for the English-speaking audience, Germany, France and other European countries.
I am making two applications because I want to minimize the risk of the application being blocked. There is always such a possibility, even if it does not violate anything.
There is also a risk that the developer account will be blocked, so I want to publish the second application in another developer account - in my partner's account.
I have read that google.play analyzes the code of applications and understands if this application was obtained by modifying another application already published in google.play. (I want to ask a related question: is this true?)
So I would like to know how should I proceed:
a) Publish a second application in my developer account and then transfer it to a partner account
or
b) It is possible to publish a second one made from the first application, right away in the partner's account and no downgrading filters will be applied to him when searching?
Thanks for answers.

Answer 1

I currently have 3 applications on Google Play with almost identical sources, they differ:
1. Naturally, by package names (set via flavors)
2. By the state of several keys that determine the status of the application (Pro/Lite) or even a set of public views for the user.
Initially, he led all applications in "different folders", then with a forced transition to Android Studio (say Eclipse everything), he pulled out all the code into one package, connected the differences through flavors.
The second year the flight is normal ...

Answer 2

Did you write to support? If not, then write.