Inconsistency in Prefix applied by various methods

Hi Team Wrike and Community,

I would like to ask assistance with an inconsistent behaviour in adding Prefixes we are experiencing and need to solve if possible.

Application of Prefix is inconsistent, and appears to be dependent on HOW project/task is created - as mentioned also here.
I am writing out our current experience in detail as behaviour even from Request Forms is not consistent.

In ALL below scenarios, user does NOT manually type the [ ] square brackets in their response.

SCENARIO 1:
Type: Project-type, created from Duplication of existing Project Template (at Space level) OR Create from Blueprint (at account level).
Method: New Project created by Duplicating existing Template Project/Creating from Blueprint. To generate the Prefix, user inputs desired prefix in optional "add prefix" box.
Result: Prefix is applied to all tasks/folders/sub-projects in format Desired Prefix with square brackets NOT applied automatically by Wrike.

SCENARIO 2:
Type: Project-type, created from Request Form.
Method: New Project created from a Request Form. To generate the Prefix, RF uses "add prefix" option, with response to Question X in the form.
Result: Prefix is applied to all tasks/folders/sub-projects in format [Desired Prefix] with [ ] square brackets applied automatically by Wrike.

SCENARIO 3:
Type: Task-type, created from Request Form.
Method: New CIT created from a Request Form. To generate the Prefix, RF uses exact same "add prefix" option as Scenario 2.
Result: Prefix is applied to CIT in format Desired Prefix with [ ] square brackets NOT applied automatically by Wrike.

Can you explain why the inconsistency to how a Prefix is generated by Wrike, is this a bug or a "feature"? (lol)
Will this inconsistency be fixed anytime soon, and/or is there a way to solve this in the here and now?

Note: In our particular case, automatic adding of [ ] square brackets is the desired outcome to the action of adding a prefix, as it 
1. Marks a clear delineation between the Project Identifier and the various Item Names in an object's title, making clear to users which part of a title is "open to editing" and which is not.
2. If [ ] is missing it is an issue for some of our API-level automations.

This inconsistent Prefix behaviour is a minefield for user-error when sometimes they need to remember to add the [ ] manually, and sometimes not.

Thanks in advance and I look forward to your comments!