If the db you are trying to connect to is SQL, MYSQL or Oracle, you can use FM's ESS feature to add the table or a view to your solution. This way you can see the real time data. To retain the corrected fields, you just need to place them in the same (or ideally a related table) in your FM solution. You just need a key to keep each record related between the tracking system table and your FM table.
I don't think connecting and showing the Oracle DB fields will be a problem. I'm having a hard time wrapping my head around how to scrub data and keep it in a seperate field. It needs to be seemless to the user. So if they are editing a title field just to add "Proactive" to the beginning of the title I want them to be able to click, add it, an move on. Everytime I think of a workaround I end up with a road block as to why it won't work.
Do your users need to make the change such as adding "proactive" again, if the data from the Oracle system changed? If so, you can set up a table that retains the data from Oracle at a point in time, and compare it to the current data. If it is different, alert the user, or put it on their "to do" list, so it can be addressed. Then update your table with the latest data, to compare to the next time the Oracle system updates. If the data does not change, then leave it as is.