You can either add Inputs with manual HTML as you did or you can use Generic Fields of Forms.
In both cases, no mechanism will save them to the database, and those inputs are just that: inputs, that will not be saving their values on submit of the form
When using generic Fields as provided by Toolset you could set a "persist:1" argument (deprecated but working), this would save the fields to that post in the database, but, it would not be editable in the backend of the post as a Toolset Field is.
This is what you found here https://toolset.com/forums/topic/save-cred-generic-field-value-to-custom-field/
In general, it is rather suggested to - if you really require such inputs and cannot do it with a Toolset field - to use a Custom code to read the data from the $_POST of the form, and update with this your target data in the database, hooking your code to a cred_save_data() hook
cred_save_data() is like a "hook" in the life-span of a Form. It is triggered exactly when you submit that form
This means you can wrap any custom code with it, and when the form is submitted that code will fire.
That code is what will read your Input data from the $_POST and using update_post_meta() WordPress API function, you could then update other fields with this.
An example can be found on our doc here https://toolset.com/documentation/programmer-reference/cred-api/#cred_save_data and in my Pastebin here https://pastebin.com/2BTbVbcs
To get a value from an input field on a form you can usually do $value = $POST['name-of-that-field']
Using this $value later in update_post_meta(), wrapped inside a cred_save_data(), allows then to update the database with the value coming from $value = $POST['name-of-that-field']
I can help with this limitedly only, I can assist and show examples, but not create the full code.
For full custom code assistance, you would have to refer to contractors, for example, https://toolset.com/contractors/
Thanks!