You can keep it all in one file, along with the code and results of its execution.
That org capture template will feed new data into a table; below it, in the same .org file, you can keep your R code and your Python code and whatever other code you prototype (I often write Elisp code), and you can execute all that code inside the .org file.
This approach is not giving you any new features, it's just optimizing for convenience. Think of .org files as Jupyter notebooks on steroids :).
I was going to say, sounds like Jupyter. Is there much of an advantage I'm missing out on as someone who prefers GUIs over the terminal and vim/emacs?
I track my blood pressure similarly. The entry is simple and I can read the csv into R/python whenever I want to visualize it.